BGrambo's profile

New Contributor

 • 

1 Message

Closed

Random Modem Errors

Been having issues with my internet for the last few days. Opened up the modem UI and noticed some errors. Anyone have any idea what could be going wrong?

Signal

DownstreamBonding Channel Value
Channel ID 22  19  20  21 
Frequency 939000000 Hz  921000000 Hz  927000000 Hz  933000000 Hz 
Signal to Noise Ratio 36 dB  36 dB  36 dB  36 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   -3 dBmV   -3 dBmV   -4 dBmV  

UpstreamBonding Channel Value
Channel ID 3  1  2  4 
Frequency 29800000 Hz  18400000 Hz  23300000 Hz  36300000 Hz 
Ranging Service ID 242  242  242  242 
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  37 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 22  19  20  21 
Total Unerrored Codewords 20967969  20967796  20967885  20967887 
Total Correctable Codewords 13  14  53  17 
Total Uncorrectable Codewords 578  758  626  665 


Logs

Jan 31 2016 11:35:43 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 11:35:43 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:41 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;CM-MAC=hidden;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:14 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:14 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:13 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:12 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:12 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:10 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:10 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:09 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:09 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:08 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:08 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:07 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 31 2016 09:37:07 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=hidden;CMTS-MAC=00:1e:be:ff:0a:b3;CM-QOS=1.1;CM-VER=3.0;

Valued Contributor

 • 

1.2K Messages

What type of issues are you experiencing, is the connection intermittent?  I can take a look at the signal levels on our end also, can you send an email to cox.help@cox.com including the account information?