Browser

Re: Modem reboots several times in the AM, especially weekdays

OK, I have gone back through the boxes outside and my wiring closet.   I loosened and tightened all coax connections and grounding posts.  I also wire brushed the copper connections to get some of the oxidation off (there wasn't much.)  I even rearranged a few wires so they weren't bent at weird angles and going across other wires.  I don't know if it'll help...

 

So, another factor I just realized would be worth mentioning...  I have the SWM Power Inserter for my DirecTV dish near all the gear in my wiring closet. 

 

It's this device:

http://blog.solidsignal.com/content.php/1066-Why-do-you-need-a-power-inserter-for-a-SWM-system

 

It's plugged into the same surge protector as the router (and ultimately, same circuit as the modem.)

 

This device powers the "SWM" system.  It connects to a splitter that amplifies the signal from the dish to the receiver in the living room through a single coax line (in the past, you needed 2, and then that was split out.) 

 

This is a completely separate system utilizing coax cabling.  The modem does not share any of the runs with DirecTV.

 

I pulled some more stats from my router and the modem.  See below.  It hasn't gone down since I touched it all today.  But, this is the time of the day there usually aren't issues.  I am going to monitor it for the next day and see how it goes.  If it goes back to flapping, I will contact support.  I will use the info provided by agentx5 to get a tech out to look at during the AM hours when I know should have the issue.

 

Thank you so much for your help everybody.  This forum is awesome.  I wish I would have discovered it sooner!

 

20-Oct9:55:34WAN Connection: Ethernet link down.
20-Oct9:56:12WAN Connection: WAN was restored.
20-Oct9:57:37WAN Connection: Ethernet link down.
20-Oct9:58:03WAN Connection: WAN was restored.
20-Oct10:06:28WAN Connection: Ethernet link down.
20-Oct10:07:00WAN Connection: WAN was restored.
20-Oct10:09:10WAN Connection: Ethernet link down.
20-Oct10:09:35WAN Connection: WAN was restored.
20-Oct10:17:10WAN Connection: Ethernet link down.
20-Oct10:17:36WAN Connection: WAN was restored.
20-Oct10:23:36WAN Connection: Ethernet link down.
20-Oct10:24:00WAN Connection: WAN was restored.
20-Oct10:28:20WAN Connection: Ethernet link down.
20-Oct10:28:46WAN Connection: WAN was restored.
20-Oct10:37:01WAN Connection: Ethernet link down.
20-Oct10:37:30WAN Connection: WAN was restored.
20-Oct11:04:11WAN Connection: Ethernet link down.
20-Oct11:04:43WAN Connection: WAN was restored.
20-Oct11:11:03WAN Connection: Ethernet link down.
20-Oct11:11:34WAN Connection: WAN was restored.
20-Oct11:15:04WAN Connection: Ethernet link down.
20-Oct11:15:40WAN Connection: WAN was restored.
20-Oct11:16:10WAN Connection: WAN was restored.
20-Oct11:24:50WAN Connection: Ethernet link down.
20-Oct11:25:16WAN Connection: WAN was restored.
21-Oct0:17:30WAN Connection: Ethernet link down.
21-Oct0:17:54WAN Connection: WAN was restored.
21-Oct5:55:16WAN Connection: Ethernet link down.
21-Oct5:55:52WAN Connection: WAN was restored.
21-Oct7:45:38WAN Connection: Ethernet link down.
21-Oct7:46:02WAN Connection: WAN was restored.
21-Oct16:48:37WAN Connection: Ethernet link down.
21-Oct16:49:01WAN Connection: WAN was restored.
21-Oct19:19:28WAN Connection: Ethernet link down.
21-Oct19:19:52WAN Connection: WAN was restored.
21-Oct19:28:23WAN Connection: Ethernet link down.
21-Oct19:28:49WAN Connection: WAN was restored.
21-Oct21:58:36WAN Connection: Ethernet link down.
21-Oct21:59:02WAN Connection: WAN was restored.
21-Oct23:10:04WAN Connection: Ethernet link down.
21-Oct23:10:28WAN Connection: WAN was restored.
21-Oct23:59:54WAN Connection: Ethernet link down.
22-Oct0:00:20WAN Connection: WAN was restored.
22-Oct0:06:30WAN Connection: Ethernet link down.
22-Oct0:06:56WAN Connection: WAN was restored.
22-Oct0:51:47WAN Connection: Ethernet link down.
22-Oct0:52:16WAN Connection: WAN was restored.
22-Oct0:52:46WAN Connection: WAN was restored.
22-Oct1:29:01WAN Connection: Ethernet link down.
22-Oct1:29:37WAN Connection: WAN was restored.
22-Oct1:30:31WAN Connection: WAN was restored.
22-Oct1:41:12WAN Connection: Ethernet link down.
22-Oct1:41:38WAN Connection: WAN was restored.
22-Oct7:05:14WAN Connection: Ethernet link down.
22-Oct7:05:40WAN Connection: WAN was restored.
22-Oct7:30:15WAN Connection: Ethernet link down.
22-Oct7:30:53WAN Connection: WAN was restored.
22-Oct7:39:17WAN Connection: Ethernet link down.
22-Oct7:39:43WAN Connection: WAN was restored.
22-Oct7:48:13WAN Connection: Ethernet link down.
22-Oct7:48:40WAN Connection: WAN was restored.
22-Oct7:59:39WAN Connection: Ethernet link down.
22-Oct8:00:15WAN Connection: WAN was restored.
22-Oct8:39:01WAN Connection: Ethernet link down.
22-Oct8:39:25WAN Connection: WAN was restored.
22-Oct8:43:00WAN Connection: Ethernet link down.
22-Oct8:43:26WAN Connection: WAN was restored.
22-Oct11:37:39WAN Connection: Ethernet link down.
22-Oct11:38:08WAN Connection: WAN was restored.
22-Oct16:14:03WAN Connection: Ethernet link down.
22-Oct16:14:35WAN Connection: WAN was restored.
22-Oct17:03:41WAN Connection: Ethernet link down.
22-Oct17:04:15WAN Connection: WAN was restored.
22-Oct18:10:26WAN Connection: Ethernet link down.
22-Oct18:10:50WAN Connection: WAN was restored.
22-Oct18:18:05WAN Connection: Ethernet link down.
22-Oct18:18:37WAN Connection: WAN was restored.
23-Oct8:43:43WAN Connection: Ethernet link down.
23-Oct8:44:09WAN Connection: WAN was restored.
23-Oct8:49:04WAN Connection: Ethernet link down.
23-Oct8:49:30WAN Connection: WAN was restored.
23-Oct8:51:05WAN Connection: Ethernet link down.
23-Oct8:51:32WAN Connection: WAN was restored.
23-Oct8:52:12WAN Connection: WAN was restored.
23-Oct8:56:02WAN Connection: Ethernet link down.
23-Oct8:56:26WAN Connection: WAN was restored.
23-Oct9:00:21WAN Connection: Ethernet link down.
23-Oct9:00:47WAN Connection: WAN was restored.
23-Oct9:01:27WAN Connection: WAN was restored.
23-Oct9:13:42WAN Connection: Ethernet link down.
23-Oct9:14:06WAN Connection: WAN was restored.
23-Oct9:22:11WAN Connection: Ethernet link down.
23-Oct9:22:35WAN Connection: WAN was restored.
23-Oct9:46:36WAN Connection: Ethernet link down.
23-Oct9:47:02WAN Connection: WAN was restored.
23-Oct10:21:52WAN Connection: Ethernet link down.
23-Oct10:22:18WAN Connection: WAN was restored.
23-Oct10:26:44WAN Connection: Ethernet link down.
23-Oct10:27:20WAN Connection: WAN was restored.
23-Oct10:31:40WAN Connection: Ethernet link down.
23-Oct10:32:06WAN Connection: WAN was restored.
23-Oct10:42:26WAN Connection: Ethernet link down.
23-Oct10:42:58WAN Connection: WAN was restored.
23-Oct10:48:43WAN Connection: Ethernet link down.
23-Oct10:49:09WAN Connection: WAN was restored.

 

Downstream Bonding Channel Value
Channel ID17 18 20 21 22 23 24 30 
Frequency555000000 Hz 561000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 633000000 Hz 
Signal to Noise Ratio36 dB 36 dB 36 dB 36 dB 36 dB 35 dB 36 dB 36 dB 
Downstream ModulationQAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
4 dBmV  4 dBmV  3 dBmV  3 dBmV  2 dBmV  3 dBmV  2 dBmV  3 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz 
Ranging Service ID5440 5440 5440 5440 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec 
Power Level42 dBmV 42 dBmV 41 dBmV 41 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID17 18 20 21 22 23 24 30 
Total Unerrored Codewords559146786 511758981 414975739 415003403 414942722 414728561 414887790 414973439 
Total Correctable Codewords483 1477 1100 1082 1547 5599 983 3994 
Total Uncorrectable Codewords6993 13634 3675 10850 3792 13583 8010 10621 
Expert

Re: Modem reboots several times in the AM, especially weekdays

reset the modems FEC counters if possible to clear out the correcteds you created by taking off connectors.   500 or so uncorrecteds are normal on those modems at startup. Then look at them in 6 hours, see if any channels have huge jumps....

 

Sharer

Re: Modem reboots several times in the AM, especially weekdays

Power, especially AC, near signals is bad.  Try to separate them as much as possible.

 

If wires have to cross, try to cross perpendicularly.

 

You were right: bend radius does matter.  However, if cables were bent too much (especially coax), it could be damaged.

Browser

Re: Modem reboots several times in the AM, especially weekdays

Well folks, the situation has improved, but its not stable yet.  I am going to contact support and use the info provided by agentx5.

 

I am unable to reset stats as the modem interface is quite limited.  Oh, but a full power cycle would do the trick right?

 

Here are the latest stats:

 

24-Oct9:06:03WAN Connection: Ethernet link down.
24-Oct9:06:32WAN Connection: WAN was restored.
24-Oct19:24:29WAN Connection: Ethernet link down.
24-Oct19:24:55WAN Connection: WAN was restored.
24-Oct19:25:25WAN Connection: WAN was restored.
24-Oct19:38:30WAN Connection: Ethernet link down.
24-Oct19:38:56WAN Connection: WAN was restored.
24-Oct19:43:31WAN Connection: Ethernet link down.
24-Oct19:43:55WAN Connection: WAN was restored.
24-Oct19:47:15WAN Connection: Ethernet link down.
24-Oct19:47:49WAN Connection: WAN was restored.
25-Oct2:18:46WAN Connection: Ethernet link down.
25-Oct2:19:20WAN Connection: WAN was restored.
25-Oct8:48:12WAN Connection: Ethernet link down.
25-Oct8:48:38

WAN Connection: WAN was restored.

 

TimePriorityCodeMessage

Oct 25 2016 07:48:546-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:48:545-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:223-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:48:013-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:313-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:293-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:293-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:293-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:283-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:283-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:283-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:283-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 07:47:283-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 02:41:163-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 02:41:163-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 02:41:153-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 01:19:236-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 25 2016 01:19:225-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

 

Downstream Bonding Channel Value
Channel ID17 18 19 20 21 22 23 24 
Frequency555000000 Hz 561000000 Hz 567000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 
Signal to Noise Ratio33 dB 33 dB 33 dB 33 dB 33 dB 32 dB 33 dB 31 dB 
Downstream ModulationQAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
7 dBmV  7 dBmV  7 dBmV  6 dBmV  7 dBmV  6 dBmV  6 dBmV  5 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz 
Ranging Service ID2421 2421 2421 2421 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec 
Power Level41 dBmV 40 dBmV 40 dBmV 40 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID17 18 19 20 21 22 23 24 
Total Unerrored Codewords37433180 36395644 36378012 36396751 36364138 36351213 36335455 36291235 
Total Correctable Codewords2949 2286 5312 9280 16055 28643 46130 91343 
Total Uncorrectable Codewords1708 532 598 607 664 647 616 622 
Expert

Re: Modem reboots several times in the AM, especially weekdays

Your s/n is really bad, Docsis 3 qam 256 becomes unreliable at 32 dBmv and doesn't work at all at 29 dBmv.

 YOUR s/N has gotten 3 dB worst and the signal level has gone up 5 dB.

 TWC HAS A BAD LINE AMPLIFIER SOMEWHERE OUT ON THE STREET, get this escallated to Tier 3 and get the bucket truck guys out to fix this (may take another inhouse tech visit to escalate the issue.

See if your neighbors have the same issues of low s/n and have them call this in as well.

 

Browser

Re: Modem reboots several times in the AM, especially weekdays

Well folks, I called support tonight and they immediatly agreed to dispatch a technician.  So tomorrow between 10AM and 12PM EST, we'll go through it!

 

I hope I get a good field tech and we come up with a solution.

Expert

Re: Modem reboots several times in the AM, especially weekdays

print out that last signal page and the good one...

tell them something is intermittently changing

 

Browser

Re: Modem reboots several times in the AM, especially weekdays

The tech concluded its either the modem, or a faulty crimped on connector that connects to the modem.  He ran several tests out on the box on the side of my house and also from that box to my modem.  They all looked good.

 

I did tell him about what we discovered here and he didn't seem convinced the issue was at the street.

 

He replaced the connection at the modem with a new compression connector.

 

Unfortunately, he could not replace my modem on-site since I own mine.

 

He said he's not a fan of the Arris modems.  he said they have a high failure rate.  I will admit to buying it refurbished from Amazon 2 years ago.  Normally i don't like to buy refurb, but they are so freaking expensive! 

 

My next steps are to go pick up a leased modem before buying a new one if it reboots again.  There is a TWC store nearby.  I am willing to pay the rental fee for a short time if that proves to be stable.

 

Off the record, he did tell me he heard that with the Charter merger going through, modem rental fees may go away.  So I see that as a big plus!  I was really annoyed when they started charging after I had been a customer for so long!

 

Here are todays stats.  It hasn't gone down since he left at 11:00 (knocks on wood!)

 

10/27/2016 0:25WAN Connection: Ethernet link down.
10/27/2016 0:25WAN Connection: WAN was restored.
10/27/2016 0:26WAN Connection: WAN was restored.
10/27/2016 0:44WAN Connection: Ethernet link down.
10/27/2016 0:44WAN Connection: WAN was restored.
10/27/2016 9:36WAN Connection: Ethernet link down.
10/27/2016 9:36WAN Connection: WAN was restored.
10/27/2016 9:54WAN Connection: Ethernet link down.
10/27/2016 9:55WAN Connection: WAN was restored.
10/27/2016 9:57WAN Connection: Ethernet link down.
10/27/2016 9:58WAN Connection: WAN was restored.
10/27/2016 9:58WAN Connection: WAN was restored.
10/27/2016 10:34WAN Connection: Ethernet link down.
10/27/2016 10:35WAN Connection: WAN was restored.
10/27/2016 10:59WAN Connection: WAN was restored.

 

Downstream Bonding Channel Value
Channel ID18 17 19 20 21 22 23 24 
Frequency561000000 Hz 555000000 Hz 567000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 
Signal to Noise Ratio36 dB 36 dB 36 dB 36 dB 37 dB 36 dB 36 dB 36 dB 
Downstream ModulationQAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
4 dBmV  4 dBmV  4 dBmV  3 dBmV  3 dBmV  2 dBmV  3 dBmV  2 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID5426 5426 5426 5426 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level42 dBmV 42 dBmV 43 dBmV 43 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID18 17 19 20 21 22 23 24 
Total Unerrored Codewords325619891 325627813 325644687 325635875 325609000 325609373 325609684 325608750 
Total Correctable Codewords85 92 197 400 666 1266 2036 4136 
Total Uncorrectable Codewords617 854 679 659 618 709 716 630 

 

TimePriorityCodeMessage

Oct 27 2016 09:59:276-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 09:59:265-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:24:303-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 09:34:313-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 09:34:315-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 09:34:293-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 09:34:073-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:58:266-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:58:265-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:203-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:57:373-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:57:073-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:55:396-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:55:395-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:55:163-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:55:156-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Oct 27 2016 08:55:155-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:203-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:87:f1:d2;CMTS-MAC=00:17:10:88:f8:27;CM-QOS=1.1;CM-VER=3.0;
Browser

Re: Modem reboots several times in the AM, especially weekdays


@MsRaye wrote:

print out that last signal page and the good one...

tell them something is intermittently changing

 


I didn't see your comment until he had already came and went!

Sharer

Re: Modem reboots several times in the AM, especially weekdays

If he really thought the modem was faulty, then he should have left a test modem.

 

Since he did not, then I'll assume that 1) he needs to keep his unqualified opinions out of the troubleshooting procedure and to himself, and/or 2) they are told/driven to get as many COAMs replaced with lucrative leases as possible.

 

When he said, "I don't think the problem is at the street", the only response to that is, "Why have you ruled that out?" and only accept a troubleshooting measure and result that makes sense.  Otherwise, it's an assumption and it's easier (for him) to assume your modem is bad rather than to call in a fix for a line when TWC is averse to rolling trucks to fix stuff.

 

F-connectors are the new placebo. Smiley Wink

 

 

You don't have to be technically knowlegeable...just dilligent.

 

"What do these T3 and T4 errors mean?"

 

"What causes them?"

 

"Would a bad connection cause them?"

 

"Do indoor modems fail more often than outdoor, weatherbeaten cables that are years older than the modem?"