2 edits | reply to Meatball
Re: SB6141 Firmware Update? I see those MIMO events quite often in my logs as well. I'm not entirely sure what they are and they do seem to appear in/around/after my stream of timeouts. I have been saving spreadsheets of the modem logs several times a day and also when I experience the timeouts first hand.
Luckily I've only had one today so far at around 2:00PM CST. There were no users on the the network at the time that this happened.
Time Priority Code Message
Dec 29 2012 14:05:13 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:52 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:19 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Dec 29 2012 14:03:56 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Dec 29 2012 14:03:26 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Dec 29 2012 14:03:16 4-Error C401.0 DCC-ACK not received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Dec 29 2012 14:03:16 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Edit: have had 4 or 5 resets between 9PM-midnight, pretty much always the same subset of messages as above. Sometimes I'll see a "16 consecutive T3 Timeouts...." message. This is driving me nuts. |
