Quantcast
Channel: Basic Internet Connectivity And Modem Help topics
Viewing all articles
Browse latest Browse all 12065

Modem T4 time out error - Received Response to Broadcast Maintenance Request.....

$
0
0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

 

 

For past 2 days I am seeing a lot of these error on my modem logs.

 

It has worked perfectly for almost 6 months now. And suddenly this has started.

 

Modem is  Motorola 6121.

 

Below are the signal stats. I dont have a splitter. Modem is directly connected to the coaxial cable

 

Downstream 

----------------

Channel ID                             3  1  2  6 

Frequency                              663000000 Hz  651000000 Hz  657000000 Hz  681000000 Hz 

Signal to Noise Ratio              37 dB  37 dB  37 dB  38 dB 

Downstream Modulation        QAM256  QAM256  QAM256  QAM256 

Power Level                            0 dBmV   0 dBmV   0 dBmV   -1 dBmV  

 

Upstream

-------------

Channel ID                             9 

Frequency                               22000000 Hz 

Ranging Service ID                10153 

Symbol Rate                           2.560 Msym/sec 

Power Level                            57 dBmV 

Upstream Modulation             [3] QPSK
[2] 16QAM
[3] 64QAM

Ranging Status                        Success 

 

Signal stats(codewords)

------------------------------

Channel ID                             3  1  2  6 

Total Unerrored Codewords   349582866  349582872  349582869  349582881 

Total Correctable Codewords 34  32  29  21 

Total Uncorrectable Codewords 642  643  649  648 

 

 

 

I chatted with comcast customer care yesterday & she went over re-starting modem & router citing that modem was out of sync with the server. And rebooting has got it into sync.

 

It worked after that till today afternoon, where it started the same problem again.

 

My logs are full of these errors.

 

Jun 16 2014 16:44:27 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

 

Jun 16 2014 16:43:37 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jun 16 2014 14:33:07 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:26:16 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:23:32 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:23:32 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:23:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:22:28 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:21:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:21:11 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:18:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:18:16 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:17:00 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:16:46 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:16:46 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:16:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:15:50 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:15:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

Jan 01 1970 00:14:33 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:92:0e:88;CMTS-MAC=00:01:5c:22:32:84;CM-QOS=1.1;CM-VER=3.0;

 

 

Not sure whats going on.

 

Can someone plz help ?


Viewing all articles
Browse latest Browse all 12065

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>