Observer

INTERNET DROPS CONNECTION OFTEN

Hello, I have an issue with my internet connection. What will happen is my internet will drop for 2 - 10 mins (sometimes longer) and I will have to reboot my modem. I can unplug the modem or reset it and this useally solves it until it happens again (that might be a few minutes or days) It happens sometimes 1 - 6 times a week. Sometimes 1 -6 times a day. Sometimes it won't happen for a few weeks. On occasion I will have to wait more than the normal 2 - 10 mins and the modem won't be able to connect for hours.  

I have INTERNET ONLY.

No phone or cable service.

I live in Louisville Ohio (zip code 44641)

Here is my modem info and the last logs from my modem from today when I lost service for a few minutes. 

 

Motorola Surfboard 


363081205103294904010006

Information
Standard Specification CompliantDOCSIS 3.0
Hardware Version1
Software VersionSBG6580-6.5.2.0-GA-06-077-NOSH
Cable Modem MAC Addresse8:6d:52:00:b0:b0
Cable Modem Serial Number363081205103294904010006
CM certificateInstalled

 

Status
System Up Time0 days 00h:03m:03s
Network AccessAllowed
Cable Modem IP Address---.---.---.---

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration File  
SecurityEnabledBPI+

 

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM2569705000000 Hz-1.2 dBmV41.3 dB00
2LockedQAM2561657000000 Hz-1.9 dBmV41.4 dB00
3LockedQAM2562663000000 Hz-1.7 dBmV41.4 dB00
4LockedQAM2564675000000 Hz-1.6 dBmV41.8 dB00
5LockedQAM2565681000000 Hz-1.6 dBmV41.4 dB00
6LockedQAM2566687000000 Hz-0.8 dBmV41.1 dB00
7LockedQAM2567693000000 Hz-0.4 dBmV41.4 dB00
8LockedQAM2568699000000 Hz-0.7 dBmV41.3 dB00

 

Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA362560 Ksym/sec37000000 Hz57.0 dBmV
2Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
3Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
4Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV

 

 

9 REPLIES
Observer

Re: INTERNET DROPS CONNECTION OFTEN

 Time  Priority  Description 
 Sun Sep 03 14:33:08 2017   Notice (6)  TLV-11 - unrecognized OID;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Sun Sep 03 14:33:07 2017   Error (4)  Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Sun Sep 03 14:33:07 2017   Error (4)  Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established  Notice (6)  WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INIT 
 Sun Sep 03 14:32:18 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:31:33 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:30:49 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:30:05 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:29:21 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:28:39 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:28:38 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:28:35 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:27:58 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Sun Sep 03 14:26:51 2017   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Sun Sep 03 14:26:35 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:25:50 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:25:04 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Sun Sep 03 14:15:34 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:14:49 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:14:06 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:14:04 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:13:25 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:13:23 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:13:20 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:12:36 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:11:52 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:11:07 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Sun Sep 03 14:10:20 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Thu Aug 31 21:48:31 2017   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
Observer

Re: INTERNET DROPS CONNECTION OFTEN

This is all I can think to provide. I have copys of logs and status during the down phase as well. 

 

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel Locked
Connectivity State In Progress Access Denied
Boot State In Progress Unknown
Configuration File
Security Disabled Disabled

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 7 693000000 Hz -0.4 dBmV 41.5 dB 12204 1724
2 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
3 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
4 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
5 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
6 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
7 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
8 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 36 2560 Ksym/sec 37000000 Hz 51.0 dBmV
2 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
3 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV


Current System Time: Sun Sep 03 14:12:56 2017

Highlighted
Expert

Re: INTERNET DROPS CONNECTION OFTEN

you have either open spliutter ports or a corroded or too short center wire at a connector.

 If you're internet only, modem must be directly connected to the outside grounding block.

 Center wire must be shiny copper and extends 1/8" beyond the nuts

 Upstream must be below +50dBmv on 4 channels at +57 it's way out of spec and is trying to concentrate all power on a single channel and is at max...

The 6580 is also an obsolete device but changing modems won't fix bad levells  It won't support IPv6 and TWC was scrapping all the leased ones.

What does TWC say when you call them on this? It cannot be fixed over the phone, needs a tech out...

 

 

Observer

Re: INTERNET DROPS CONNECTION OFTEN

They say the same. Can't be fixes would I like  a Tech. I haven't due to past experiances of nothing being resolved.  You suggest I should make an appointment? 

 

I inspected where my cable enters the house (it is a mess of cables and 3 spitters from switching from  Direct TV to TWC years ago) and I noticed that from the outside it is running to a 3 way splitter with one line connected and two empty connections everything else is unscrewed and not connected to anything.   (Now I know why my modem only connects in one room)

 

If it should be connected directly to the outsided grounding block then it should just be from outside stirght to my modem (no splitters at all)?

 

 Do i need to have something on all three of the splitter pegs?

Just use the cables going to empty rooms to cap the splitter or find some 75ohm caps for the empty ones?

 

 

Observer

Re: INTERNET DROPS CONNECTION OFTEN

If it is supposed to be direct from outside to the modem should i just use a coaxial cable coupler to connect it?

Expert

Re: INTERNET DROPS CONNECTION OFTEN

There should be a grounding block before the splitter.. Connect the modem directly to it.

sometimes they used the splitter as the grounding block,  if the 3 way is marked -3.5  -7   -7, put the modem on the -3.5 dB port and screw terminators on the -7 dB ports... \ I'll bet a grounding block is the same price as 2 terminating resistors, lol.

 

Observer

Re: INTERNET DROPS CONNECTION OFTEN

Same issue on one line stright from modem to block. Lost connection in the same manner a few times in the past few days and this morning for over an hour. 

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration File  
SecurityEnabledBPI+

 

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM2567693000000 Hz5.6 dBmV41.5 dB00
2LockedQAM2568699000000 Hz5.3 dBmV41.9 dB00
3LockedQAM2569705000000 Hz5.2 dBmV41.2 dB00
4LockedQAM25610711000000 Hz4.9 dBmV41.5 dB00
5LockedQAM25611717000000 Hz4.9 dBmV41.3 dB00
6LockedQAM25614735000000 Hz4.4 dBmV40.3 dB00
7LockedQAM25615741000000 Hz4.3 dBmV40.7 dB00
8LockedQAM25616747000000 Hz3.7 dBmV40.4 dB00

 

Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA355120 Ksym/sec30600000 Hz37.5 dBmV
2LockedTDMA332560 Ksym/sec19400000 Hz37.5 dBmV
3LockedATDMA345120 Ksym/sec24200000 Hz37.5 dBmV
4LockedATDMA362560 Ksym/sec37000000 Hz37.5 dBmV



Current System Time: Fri Sep 08 07:48:50 2017

 

 

Observer

Re: INTERNET DROPS CONNECTION OFTEN

 Time  Priority  Description 
 Fri Sep 08 07:42:16 2017   Notice (6)  TLV-11 - unrecognized OID;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Fri Sep 08 07:42:16 2017   Error (4)  Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Fri Sep 08 07:42:16 2017   Error (4)  Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Fri Sep 08 07:42:16 2017   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Fri Sep 08 07:42:02 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:41:52 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:41:31 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:41:21 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:41:13 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:41:03 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:40:29 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:40:19 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:39:53 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:39:43 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:39:22 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:39:12 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:38:58 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:38:48 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:38:29 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:38:19 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:38:03 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:37:21 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:37:20 2017   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:37:17 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:37:07 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:36:35 2017   Warning (5)  B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:36:35 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:35:40 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:35:30 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:35:25 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:35:15 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:34:30 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:34:20 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:34:11 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:34:00 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:33:51 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:33:41 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:33:37 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:33:27 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:33:10 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:33:00 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:32:52 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:32:42 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:32:28 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:32:18 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:32:09 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:31:59 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:31:45 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:31:35 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:31:30 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:31:20 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:30:53 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:30:43 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:30:37 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:30:27 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:30:01 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:29:51 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:29:43 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:29:32 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:28:49 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:28:39 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:27:49 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:27:39 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:27:11 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:27:01 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:26:49 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:26:39 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:26:21 2017   Warning (5)  B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:26:21 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:25:07 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:24:57 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:24:42 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:24:32 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:24:20 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:24:10 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:23:47 2017   Warning (5)  B-INIT-RNG Failure - Retries exceeded;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:23:47 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:22:38 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:22:28 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:21:59 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:21:49 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:21:25 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:21:15 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:20:43 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:20:33 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:20:20 2017   Critical (3)  No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.0;CM-VER=3.0; 
 Fri Sep 08 07:20:10 2017   Critical (3)  No Ranging Response received - T3 time-out  
 Fri Sep 08 07:19:49 2017   Notice (6)  T4 No Station Maint Timeout - Reinitialize MAC... 
 Fri Sep 08 07:19:49 2017   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Fri Sep 08 07:19:16 2017   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Fri Sep 08 07:18:02 2017   Notice (6)  TLV-11 - unrecognized OID;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Fri Sep 08 07:18:02 2017   Error (4)  Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
 Fri Sep 08 07:18:02 2017   Error (4)  Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e8:6d:52:00:b0:b0;CMTS-MAC=00:01:5c:81:cc:62;CM-QOS=1.1;CM-VER=3.0; 
Expert

Re: INTERNET DROPS CONNECTION OFTEN

Levels are now correct and the open splitter ports were a major issue... You need TWC out to figgure what is wrong on the node, and it's probably numerous other customers with open ports and bad connections.  You at least have the proper 8x4 bonding.