Valued Participant

Re: Yet another SB6141 related issue?

MsRaye typed:

>so it looks like the DS partial services occurred when it was windy?

 

Like I typed previously, 'breezy'.  I.e., not really windy yesterday.  The drop in temps was the larger weather event these last few days.

 

>Can you get a picture under the amp looking up? it looks like the lines kinked/broken there

 

Two more pics up this a.m. labelled 'Mar 21, 2016' taken standing at the corner of my property as close as I can get to be underneath the hardware.  Unfortunately, the amp is positioned more towards my next door neighbors' property rendering most of the connection point on the left side of the amp out of sight.  AT&T's fiber installation just below kind of obsures the view as well but nothing I can do about that.

 

I'm going to check with my neighbor tonight when they get home from work to see if they will premit me on their property to take a few pics in the a.m. tomorrow?

 

.

Expert

Re: Yet another SB6141 related issue?

This is bad.... unknown if it's broken but it was caused by no strain relief/ expansion bend on the left of the amp and the drop that's attached right in back of the amp.

Valued Participant

Re: Yet another SB6141 related issue?

Took a dozen more pics (labeled Mar 22, 2016) with a better view of the left side of the amp this a.m.

 

Signal 30 minutes ago:

DownstreamBonding Channel Value
Channel ID10 
Frequency501000000 Hz 513000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 555000000 Hz 
Signal to Noise Ratio38 dB 39 dB 38 dB 37 dB 37 dB 39 dB 39 dB 
Downstream ModulationQAM256 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  6 dBmV  6 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID7410 7410 7410 7410 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level48 dBmV 47 dBmV 48 dBmV 47 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 ID10 
Total Unerrored Codewords6525072048 6401918649 6372228325 6372263518 6372169216 6372159021 6372155355 
Total Correctable Codewords15 83 52 84 134 95 90 
Total Uncorrectable Codewords592 1200 1873 1749 2970 2062 1834 

 

Signal now:

DownstreamBonding Channel Value
Channel ID10 11 
Frequency501000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 555000000 Hz 561000000 Hz 
Signal to Noise Ratio38 dB 39 dB 39 dB 39 dB 39 dB 39 dB 39 dB 
Downstream ModulationQAM256 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  6 dBmV  6 dBmV  6 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID7410 7410 7410 7410 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level48 dBmV 47 dBmV 48 dBmV 47 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 ID10 11 
Total Unerrored Codewords6564247036 6421506798 6391831876 6391882999 6391751164 6391741967 6391739518 
Total Correctable Codewords15 95 65 93 173 109 106 
Total Uncorrectable Codewords592 1802 2522 2387 3650 2737 2414 

  

 And the log:

TimePriorityCodeMessage

Mar 21 2016 10:25:315-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2016 10:25:315-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 20 2016 17:54:596-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 20 2016 17:54:585-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 20 2016 17:54:316-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 20 2016 17:54:315-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 22:26:403-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 21:56:455-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 21:56:455-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 21:56:455-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 21:56:455-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 18 2016 15:32:285-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 18 2016 15:32:285-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 17 2016 22:00:296-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 17 2016 22:00:285-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 17 2016 22:00:006-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 17 2016 22:00:005-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 17 2016 20:45:406-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 

.

Expert

Re: Yet another SB6141 related issue?

This is bad.... The aluminum hardline is not tightly wrapped to the messenger cable

So it's moving more in the wind

 

Expert

Re: Yet another SB6141 related issue?

And this needs to be cut open and examined: As the drop to the house behind you blows in the wind, , it flexes this joint and probably has broken it.   That drop needs to be anchored closer to the pole if not directly to the pole. It's a sloppy inexperienced installation.  The left hand line which i believe is the input side is also missing the dog leg expansion loop  . It's also a really old instal using bare aluminum line rather than the plastic jacketed

 

 

 

Expert

Re: Yet another SB6141 related issue?

Here's one that's properly installed but sorta messy because this is the main node where fiber is converted to coax and then split 4 ways to feed 4 streets.

 there are expansion loops on both sides of the amp.

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye ==> Thanks again for your observations!

 

Very windy here today.  I don't have an anemometer but the forecast was 20 mph with gusts to 30+ and I beleive they got the forecast right for a change.  I could see the amp shaking side-to-side so there is obvious stress on those connects.  With three TWC drops shaking around in the wind, not to mention the three power laterals, plus a lateral to a street light out at the street, it seemed the pole was doing a bit of movement as well?

 

At any rate, down to five DS channels now.  Speed is dropping as well.  I'm a bit surprised I can still access the SB6141's embedded webserver at the moment.

 

Signal:

DownstreamBonding Channel Value
Channel ID
Frequency501000000 Hz 507000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 
Signal to Noise Ratio38 dB 40 dB 39 dB 39 dB 39 dB 
Downstream ModulationQAM256 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  6 dBmV  6 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID7410 7410 7410 7410 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level48 dBmV 47 dBmV 48 dBmV 47 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 ID
Total Unerrored Codewords7863032644 7695281464 7665617834 7665675792 7665502156 
Total Correctable Codewords16 115 82 146 184 
Total Uncorrectable Codewords592 2478 3158 3977 4248 

 

The log:

TimePriorityCodeMessage

Mar 22 2016 16:23:195-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 16:23:195-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 16:23:195-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 16:23:195-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2016 10:25:315-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2016 10:25:315-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 20 2016 17:54:596-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 20 2016 17:54:585-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 20 2016 17:54:316-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 20 2016 17:54:315-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 22:26:403-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 21:56:455-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 21:56:455-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 21:56:455-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 21:56:455-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 18 2016 15:32:285-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 18 2016 15:32:285-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 17 2016 22:00:296-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 17 2016 22:00:285-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 

.

Expert

Re: Yet another SB6141 related issue?

If you look at my photo,The  \___/  should be on the left of your amp as well.  This needs the boom truck guys out and yeah, they're going to have to drag ladders back there and splice in a new length of line, and change out the "stinger" that adapts the hardline to the amp housing....

Any of the house/ line techs should be able to put a meter on the 4th tap and shake the amp to see if the s/n degrades or ingress occurs. There's probably also egress they can measure

 

Did the 2 DS partial service errors occur during wind gusts?

If you saw the amp bouncing around, it's partially due to the drop that's attached to the messenger behind it tugging on it in the wind. That drops messenger hook needs to be moved close to the pole to prevent further damage.

 The work is going to PO everyone downstream, This might not be the only problem but chances are it's bad

 

 

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye types: >If you look at my photo,The  \___/  should be on the left of your amp as well.

 

Yes, I completely understand why that's necessary.

 

>This needs the boom truck guys out and yeah, they're going to have to drag ladders back there and splice in a new length of line, and change out the "stinger" that adapts the hardline to the amp housing....

...

> The work is going to PO everyone downstream,...

...

> If you saw the amp bouncing around, it's partially due to the drop that's attached to the messenger behind it tugging on it in the wind. That drops messenger hook needs to be moved close to the pole to prevent further damage.

 

Probably why nothing's happening?  Apparently I'm the only one complaining at this point?  I found out the other day that my next door neighbor has no TV and TWC's 3 Mbps down/? Mbps up, what do they call it, 'Lite' ?  Yow!  At that speed, what's a problem?  Only if there no Internet at all, I guess?  LOL

 

>Did the 2 DS partial service errors occur during wind gusts?

 

Honestly the DS partials happen so often/randomly I can't really say the wind is the cause.

 

Side note:  Cablemodem was down to 5 DS channels last night, decided to give Arris a call.  On the phone with Arris support for 30+ mins.  Finally they had me do another 'Reset All Defaults'.  Said I did the previous 'Reset All ...' wrong .  End of story, Arris support guy I talked to is forwarding the numbers I gave for DS Signal channel to Noise Ratio, Power Levels and US channel Power Levels to another department for review.  Support said I'd get a callback 'in a couple of days'.

 

FWIW, here's the Arris support's recommendation for 'Reset All Default' on the SB6141 (customer owned):

  • Using a brower connect to: 192.168.100.1
  • Go to 'Configuration' in the menu
  • Disconnect coaxial cable from SB6141 (I had not done this in my previous 'Reset All...')
  • Click on 'Reset All Defaults' (you will probably lose the browser page altogether at this point)
  • Unplug SB6141's power cord
  • Wait 30+ seconds
  • Re-connect coaxial cable
  • Re-connect power cord

If all goes wel, TWC will reprovision the cablemodem automagically and you're on the Internet once the LEDs stabilize.  If reprovisioning _does_not_ occur, you have to call TWC to get reprovisioning done (last night I _did_not_ have to call TWC.).

 

 

Of course last night after the 'Reset All...' and reboots I had 8 DS channels.  Now down to 6 DS channels...

 

Signal:

DownstreamBonding Channel Value
Channel ID
Frequency501000000 Hz 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 
Signal to Noise Ratio38 dB 39 dB 39 dB 39 dB 38 dB 39 dB 
Downstream ModulationQAM256 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  6 dBmV  6 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID1423 1423 1423 1423 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 46 dBmV 48 dBmV 46 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 ID
Total Unerrored Codewords4288079689 4143386798 4143447289 4143452152 4143316395 4143343021 
Total Correctable Codewords110 64 59 66 110 
Total Uncorrectable Codewords553 2494 2562 2526 3339 2483 

 

And logs:

 

TimePriorityCodeMessage

Mar 23 2016 20:12:405-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2016 20:12:405-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2016 13:43:315-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2016 13:43:315-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:21:416-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:21:415-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:21:136-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:21:135-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:08:476-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:08:475-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:08:196-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:08:195-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:05:233-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:05:225-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:05:213-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:05:205-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:05:193-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 22 2016 19:04:583-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 

.

 

 

Expert

Re: Yet another SB6141 related issue?

You're also getting T4's that are a long T3 and those are resetting the modem.