Highlighted
Participant

What is the Problem with this?

My modem seems to reboot all the blasted time.

 

I see this in the log.   What gives?

 

Oct 26 2017 17:52:226-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 26 2017 17:52:225-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 26 2017 17:51:253-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 26 2017 17:51:225-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 26 2017 17:50:583-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 26 2017 17:42:295-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 26 2017 17:42:295-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 24 2017 00:18:163-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:26:456-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:26:455-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:25:533-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:25:533-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:25:463-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:25:463-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:25:463-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:25:463-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:25:463-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 23 2017 00:25:463-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
11 REPLIES 11
MKE
Newcomer

Re: What is the Problem with this?

Same thing happening with me.  First they came out and said connections were loose.  Well, here we go again, which is why I am wasting my time on this **bleep** support website looking for answers.  Remote is slow to respond.  Wi-Fi times out almost every 15 minutes for about 10 seconds.  i call customer support.  They say I have an old modem and router (I just switched to this crap from AT&T 3 months ago).  Service person comes out says I have the newest modem and router.  What the hell.

Expert

Re: What is the Problem with this?

How about pasting the signal level page...

Proven Sharer

Re: What is the Problem with this?

You could also include the modem's model number and whether you rent or own it.  We're not mind readers - just sayin'!

Participant

Re: What is the Problem with this?

ARRIS SB1641 Own it.

Participant

Re: What is the Problem with this?

DownstreamBonding 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 Ratio37 dB 37 dB 37 dB 37 dB 36 dB 37 dB 37 dB 37 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
2 dBmV  1 dBmV  2 dBmV  1 dBmV  2 dBmV  2 dBmV  2 dBmV  3 dBmV  

 

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

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID17 18 19 20 21 22 23 24 
Total Unerrored Codewords8818013 8006034 7994250 8014315 7988101 7986879 7982485 7988031 
Total Correctable Codewords10 43 49 15 
Total Uncorrectable Codewords476 594 566 501 652 604 615 733 
Participant

Re: What is the Problem with this?

Problem happened again just now...  Thanks

Expert

Re: What is the Problem with this?

looks like it could be a loose or corroded connection.. Maybe broadcast tv ingress... need to see the level page ahain, hopefull with a few hours of run time after a reset...

 

Participant

Re: What is the Problem with this?

Here is after having been run for quite a while:

 

 

DownstreamBonding 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 Ratio37 dB 37 dB 38 dB 37 dB 36 dB 37 dB 37 dB 37 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
1 dBmV  1 dBmV  2 dBmV  1 dBmV  2 dBmV  2 dBmV  2 dBmV  2 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 37000000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID2137 2137 2137 2137 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level43 dBmV 43 dBmV 43 dBmV 43 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID17 18 19 20 21 22 23 24 
Total Unerrored Codewords4646170 3795829 3804014 3787296 3778238 3778431 3778008 3782323 
Total Correctable Codewords13 15 16 
Total Uncorrectable Codewords601 598 585 493 601 1406 689 

665 

 

 

 

 

 

 

 

 

TimePriorityCodeMessage
Nov 02 2017 19:04:556-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Nov 02 2017 19:04:555-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Nov 02 2017 19:04:284-ErrorU101.0TCS Fail on all Upstream Channels;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Nov 02 2017 19:04:283-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Nov 02 2017 19:04:235-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Nov 02 2017 19:04:215-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Nov 02 2017 19:03:583-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:53:146-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:53:145-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:52:203-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:52:205-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:52:193-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:52:195-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:52:183-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:51:553-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:48:035-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:48:035-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 20:47:406-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Oct 31 2017 19:39:005-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: What is the Problem with this?

Sorry but the signal pages error counts were reset by this line:

Nov 02 2017 19:04:284-ErrorU101.0TCS Fail on all Upstream Channels;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:39:90;CM-QOS=1.1;CM-VER=3.0;

 you have some sort of coaxial issue, causing that plus the RCS/DS partial service errors that indicate ingress... Try posting the signal page again