Forum Discussion

Seer's avatar
Seer
New Contributor

Too many T3 Timeouts

Well here we go again now what?  Have had to restart the modem and router to get any kind of connectivity back.  Cox sent a tech out who replaced all the fittings on the cabling in my home and from what I have seen this could be a router issue?  ANy ideas

Thanks in advance

Dec 10 2016 16:21:25

3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 10 2016 16:21:24 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 10 2016 16:21:24 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:53:50 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:53:50 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:38 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:38 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:37 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:37 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:36 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:36 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:35 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
Dec 08 2016 13:06:35 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;

Channel ID

62  59  60  61 
Frequency 975000000 Hz  957000000 Hz  963000000 Hz  969000000 Hz 
Signal to Noise Ratio 37 dB  37 dB  37 dB  37 dB 
Downstream Modulation 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   6 dBmV   5 dBmV   4 dBmV  
Upstream Bonding Channel Value
Channel ID 3  1  2  4 
Frequency 29800000 Hz  18400000 Hz  23300000 Hz  36300000 Hz 
Ranging Service ID 501  501  501  501 
Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
Power Level 35 dBmV  32 dBmV  33 dBmV  35 dBmV 
Upstream Modulation [3] 16QAM
[3] 64QAM
 		 [3] QPSK
[2] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 
Ranging Status Success  Success  Success  Success 
Signal Stats (Codewords)Bonding Channel Value
Channel ID 62  59  60  61 
Total Unerrored Codewords 46272679  45332050  45332436  45332526 
Total Correctable Codewords 9  16  1  0 
Total Uncorrectable Codewords 600  747  530 

579 

10 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • Omoeba's avatar
    Omoeba
    New Contributor

    You got a way to low power level (anything below 40 dbmv will not work)

  • grymwulf's avatar
    grymwulf
    Contributor II

    Less than 40dBmV will work (I get 120 - 190Mbps usually with Tx in the 32-34dBmV range) - certain modems accept it better than others, and it is sub-optimal.  But it doesn't categorically stop working or cause issues.

  • Seer's avatar
    Seer
    New Contributor

    My hardware is a Motorola SB6120 Modem

    Router is a Netgear WNR2000

    I know they are a little older but have been working just fine and how do I adjust the power in my modem if I can at all?

  • grymwulf's avatar
    grymwulf
    Contributor II

    Basically looking at your log, the most issues where on the 8th of December, nothing for the 9th, and 1 on the 10th.  Also on the 8th, they occurred all around the same time, which usually implies an outage or other physical disconnect.  Keep an eye on the problem, but 1 or 2 t3 errors per day not usually that unusual.  It's when they happen in 5-10 events in any 2 hour period over a period of time.  T3s will happen if a tech needs to adjust something at a node, restarting or adjusting something on the CMTS at the plant, or any of several other normal maintenance activities.

    What is the problem you are experiencing for your usage?  Exact error messages if possible?

    (And you really can't adjust the power on your modem, the most that would be recommended is putting an attenuater on your line.)

  • Seer's avatar
    Seer
    New Contributor

    I have had to reset the modem several times over the last week all for the same reason and my log is only so long so when I get into it the page is full of T3 timeouts.  I can start keeping a record of them but it seems to happen every 2 to 3 days almost like a buffer filling up and not refreshing in a pc

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Seer

    At the present the modem logs don't look all that bad. I'd suggest trying to test the connection without the router to see if the issue remains.

  • Seer's avatar
    Seer
    New Contributor

    And again it happens

    Channel ID

    62  59  60  61 
    Frequency 975000000 Hz  957000000 Hz  963000000 Hz  969000000 Hz 
    Signal to Noise Ratio 37 dB  37 dB  37 dB  37 dB 
    Downstream Modulation 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
    		6 dBmV   7 dBmV   6 dBmV   6 dBmV  
    Upstream Bonding Channel Value
    Channel ID 3  1  2  4 
    Frequency 29800000 Hz  18400000 Hz  23300000 Hz  36300000 Hz 
    Ranging Service ID 501  501  501  501 
    Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
    Power Level 33 dBmV  30 dBmV  32 dBmV  35 dBmV 
    Upstream Modulation 16QAM
         		 [3] QPSK
    [2] 16QAM
    [3] 64QAM
         		 16QAM
         		 16QAM
     
    Ranging Status Aborted  Success  Aborted  Aborted 
    Signal Stats (Codewords)Bonding Channel Value
    Channel ID 62  59  60  61 
    Total Unerrored Codewords 25530163822  25529224024  25529212427  25529209487 
    Total Correctable Codewords 134426  153001  152829  149443 
    Total Uncorrectable Codewords 12637  36590  33972 

    25869 

    Dec 17 2016 02:38:32

    3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:32 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:32 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:31 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:30 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:29 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:28 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:28 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:27 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:26 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:25 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:25 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:24 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:24 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:23 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:23 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 17 2016 02:36:22 3-Critical R07.0

    Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;

    This is getting quite old as it happenned in July 2016 and was corrected and it has started again

  • Seer's avatar
    Seer
    New Contributor

    This is after the reboot

    Channel ID

    62  59  60  61 
    Frequency 975000000 Hz  957000000 Hz  963000000 Hz  969000000 Hz 
    Signal to Noise Ratio 37 dB  37 dB  37 dB  37 dB 
    Downstream Modulation 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
    		6 dBmV   7 dBmV   7 dBmV   6 dBmV  
    Upstream Bonding Channel Value
    Channel ID 3  1  2  4 
    Frequency 29800000 Hz  18400000 Hz  23300000 Hz  36300000 Hz 
    Ranging Service ID 501  501  501  501 
    Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
    Power Level 33 dBmV  30 dBmV  31 dBmV  33 dBmV 
    Upstream Modulation [3] 16QAM
    [3] 64QAM
         		 [3] QPSK
    [2] 16QAM
    [3] 64QAM
         		 [3] 16QAM
    [3] 64QAM
         		 [3] 16QAM
    [3] 64QAM
     
    Ranging Status Success  Success  Success  Success 
    Signal Stats (Codewords)Bonding Channel Value
    Channel ID 62  59  60  61 
    Total Unerrored Codewords 38902504  38195195  38195372  38195550 
    Total Correctable Codewords 22  0  0  0 
    Total Uncorrectable Codewords 647  548  515  478 
  • Seer's avatar
    Seer
    New Contributor

    And again once yesterday and another today

    Dec 18 2016 16:43:59

    3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:43:55 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:43:55 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:38 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:38 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:38 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:38 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:37 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:37 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:37 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:37 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:36 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:36 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:35 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 16:01:35 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;

    Channel ID

    62  59  60  61 
    Frequency 975000000 Hz  957000000 Hz  963000000 Hz  969000000 Hz 
    Signal to Noise Ratio 37 dB  37 dB  37 dB  37 dB 
    Downstream Modulation 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
    		5 dBmV   7 dBmV   6 dBmV   5 dBmV  
    Upstream Bonding Channel Value
    Channel ID 3  1  2  4 
    Frequency 29800000 Hz  18400000 Hz  23300000 Hz  36300000 Hz 
    Ranging Service ID 501  501  501  501 
    Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
    Power Level 33 dBmV  31 dBmV  32 dBmV  35 dBmV 
    Upstream Modulation [3] 16QAM
    [3] 64QAM
         		 [3] QPSK
    [5] 16QAM
         		 16QAM
         		 [3] 16QAM
    [3] 64QAM
     
    Ranging Status Success  Success  Success  Success 
    Signal Stats (Codewords)Bonding Channel Value
    Channel ID 62  59  60  61 
    Total Unerrored Codewords 9788645  9036687  9036777  9036955 
    Total Correctable Codewords 0  0  0  0 
    Total Uncorrectable Codewords 511  538  594 

    554 

  • Seer's avatar
    Seer
    New Contributor

    2 times on 12/18

    Dec 18 2016 18:24:53

    3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 18:00:20 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 18:00:20 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:35 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:34 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:34 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:33 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:33 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:31 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:30 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:29 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:28 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:28 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;
    Dec 18 2016 17:48:26 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:10:3b:7a:74;CMTS-MAC=00:14:f1:e8:d3:75;CM-QOS=1.1;CM-VER=3.0;