Bray918's profile

Bray918

New Contributor III

 • 

42 Messages

Closed

Acceptable Limits on Correctable and Unorrectable

What is the acceptable amount of correctable and uncorrectable in a 24hr period? I feel like this is extreme.


Acquire Downstream Channel 951000000 Hz Locked

Upstream Connection OK Operational

Boot State OK Operational


Configuration File OK

Security Enabled BPI+


Connection Status
System Up Time 0 days 23h:40m:58s

Network Access Allowed


Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 29 951.0 4.4 39.5 2580 241
2 Locked QAM256 1 783.0 4.8 40.3 2243 1628
3 Locked QAM256 5 807.0 5.2 40.4 2741 3432
4 Locked QAM256 9 831.0 5.2 40.7 209900 39692
5 Locked QAM256 13 855.0 4.9 40.6 119785 34245
6 Locked QAM256 17 879.0 5.0 40.2 1891 681
7 Locked QAM256 21 903.0 4.9 40.2 64689 28287
8 Locked QAM256 23 915.0 5.0 40.2 72413 28925
9 Locked QAM256 24 921.0 4.9 39.9 82195 31734
10 Locked QAM256 25 927.0 4.7 39.9 95270 29917
11 Locked QAM256 26 933.0 4.6 39.8 116089 31560
12 Locked QAM256 27 939.0 4.3 39.5 133096 30622
13 Locked QAM256 28 945.0 4.4 39.6 70077 26768
14 Locked QAM256 30 957.0 4.4 39.6 110119 30746
15 Locked QAM256 31 963.0 4.5 39.6 93904 29757
16 Locked QAM256 32 969.0 4.4 39.6 87757 33036
17 Locked QAM256 33 357.0 6.3 40.5 467449 52912
18 Locked QAM256 34 363.0 5.5 40.4 415306 49387
19 Locked QAM256 35 369.0 5.3 40.4 3747 8772
20 Locked QAM256 36 375.0 5.0 40.5 418575 54701
21 Locked QAM256 37 381.0 5.3 40.6 310469 43949
22 Locked QAM256 38 387.0 5.8 41.1 178866 37954
23 Locked QAM256 39 393.0 7.0 41.6 128389 31161
24 Locked QAM256 40 399.0 7.9 41.9 115892 28391
25 Locked QAM256 41 405.0 8.6 42.0 100717 30032
26 Locked QAM256 42 411.0 9.1 42.0 65409 28498
27 Locked QAM256 43 417.0 9.0 41.8 41463 26473
28 Locked QAM256 44 423.0 8.5 41.6 42439 27036
29 Locked QAM256 45 429.0 7.5 41.2 44084 27819
30 Locked QAM256 46 435.0 6.6 40.9 52281 25142
31 Locked QAM256 47 441.0 5.9 40.9 61950 28740
32 Locked QAM256 48 447.0 5.3 40.7 117529 29815
33 Locked OFDM PLC 159 300.0 9.4 43.3 40384231 145717


Upstream Bonded Channels

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked SC-QAM 1 5120 19.3 45.8
2 Locked SC-QAM 2 5120 25.8 45.8
3 Locked SC-QAM 3 5120 32.2 45.8
4 Locked SC-QAM 4 5120 38.6 46.8

Discussions

 • 

Updated 

8.8K

8

0

0

B

Bruce

+4 more

Honored Contributor III

 • 

5.7K Messages

Typically you'll see 1 or 2 channels with high error counts caused by electronics interfering on a specific frequency.  However, you have errors on almost all channels.  Your SNR looks okay.

You could try rebooting.

1

0

B
Bray918

New Contributor III

 • 

42 Messages

I have tried that several times. just gave it a few hrs before the 24 hr run on a brand spanking new MB8600 to look at all the channels and wow, looks about the same as the cm600 and sb6141 and... Tired of it, I would change providers if I could.

Will this effect my data usage?

Like

Reply

B

Bray918

New Contributor III

 • 

42 Messages

7 Hour run

 Acquire Downstream Channel 807000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 07h:45m:50s  
  
   Network Access Allowed  
  



   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 5 807.0 5.2 40.7 944 3980
   2 Locked QAM256 1 783.0 4.6 40.5 6089 20906
   3 Locked QAM256 2 789.0 4.7 40.4 28352 124453
   4 Locked QAM256 3 795.0 4.7 40.5 29119 124664
   5 Locked QAM256 4 801.0 4.9 40.5 28722 122162
   6 Locked QAM256 6 813.0 5.2 40.7 28240 120689
   7 Locked QAM256 7 819.0 5.1 40.7 27815 120201
   8 Locked QAM256 8 825.0 5.3 40.8 27267 114937
   9 Locked QAM256 9 831.0 5.4 40.9 25425 67662
   10 Locked QAM256 10 837.0 5.2 40.8 27607 116493
   11 Locked QAM256 11 843.0 5.3 40.8 28005 114245
   12 Locked QAM256 12 849.0 5.4 41.0 28047 116941
   13 Locked QAM256 13 855.0 5.1 40.7 27658 112916
   14 Locked QAM256 14 861.0 5.0 40.7 29118 127048
   15 Locked QAM256 15 867.0 4.9 40.7 26850 102945
   16 Locked QAM256 16 873.0 5.0 40.8 19852 72688
   17 Locked QAM256 17 879.0 4.9 40.6 18225 83383
   18 Locked QAM256 18 885.0 4.9 40.5 19084 81080
   19 Locked QAM256 19 891.0 4.9 40.5 161957 79833
   20 Locked QAM256 20 897.0 4.9 40.4 3005569 524812
   21 Locked QAM256 21 903.0 4.9 40.4 26775 109793
   22 Locked QAM256 22 909.0 5.0 40.3 1952427 521440
   23 Locked QAM256 23 915.0 5.0 40.4 467675 85518
   24 Locked QAM256 24 921.0 4.8 40.4 20174 71819
   25 Locked QAM256 25 927.0 4.6 40.1 27743 116618
   26 Locked QAM256 26 933.0 4.4 40.0 17897 84266
   27 Locked QAM256 27 939.0 4.0 39.8 20011 96866
   28 Locked QAM256 28 945.0 4.0 39.8 17815 83767
   29 Locked QAM256 29 951.0 3.9 39.7 19496 90697
   30 Locked QAM256 30 957.0 3.7 39.6 20200 94501
   31 Locked QAM256 31 963.0 3.8 39.8 27343 116550
   32 Locked QAM256 32 969.0 4.0 39.8 34966 126164
   33 Locked OFDM PLC 159 300.0 9.6 44.3 2037365 71941



   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 19.3 46.3
   2 Locked SC-QAM 2 5120 25.8 46.0
   3 Locked SC-QAM 3 5120 32.2 45.8
   4 Locked SC-QAM 4 5120 38.6 46.8

0

B

Bray918

New Contributor III

 • 

42 Messages

So, is this affecting my data usage?

2

1
1486374269

New Contributor II

 • 

5 Messages

Yes.  A quote from NetForecast in a paper specifically addressing the accuracy of the Cox "data meter":

Packet loss adds to the meter

Any reliable end-to-end protocol (like TCP) has a mechanism to retransmit packets lost in transit. Packet loss will add to the traffic seen by the meter in some situations.

So the worse your service, the more you pay if you exceed the data cap.  Neat.

Like

Reply

0

B
Bray918

New Contributor III

 • 

42 Messages

Thank you for answering, and I posted another two days below. It's out of hand...

Like

Reply

0

B

Bray918

New Contributor III

 • 

42 Messages

  Acquire Downstream Channel 879000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 2 days 06h:32m:29s  
  
   Network Access Allowed  
  



   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 17 879.0 4.2 40.0 2311044 215165
   2 Locked QAM256 1 783.0 4.6 40.1 158771 132645
   3 Locked QAM256 2 789.0 4.5 40.0 165278 128683
   4 Locked QAM256 3 795.0 4.3 40.0 165950 130734
   5 Locked QAM256 4 801.0 4.4 40.1 157325 136612
   6 Locked QAM256 5 807.0 4.7 40.2 3038561 196218
   7 Locked QAM256 6 813.0 4.7 40.1 135646 166720
   8 Locked QAM256 7 819.0 4.6 40.3 154880 112618
   9 Locked QAM256 8 825.0 4.8 40.4 142896 92974
   10 Locked QAM256 9 831.0 5.0 40.3 1408199 283567
   11 Locked QAM256 10 837.0 4.8 40.3 140378 89941
   12 Locked QAM256 11 843.0 4.7 40.4 138540 89499
   13 Locked QAM256 12 849.0 5.0 40.5 141377 89384
   14 Locked QAM256 13 855.0 5.1 40.4 148751 96060
   15 Locked QAM256 14 861.0 5.3 40.3 166626 96455
   16 Locked QAM256 15 867.0 5.0 40.3 141505 91971
   17 Locked QAM256 16 873.0 4.6 40.2 957442 294426
   18 Locked QAM256 18 885.0 4.2 40.1 1338300 313037
   19 Locked QAM256 19 891.0 4.5 40.0 3533133 321136
   20 Locked QAM256 20 897.0 4.7 39.9 5255718 2739440
   21 Locked QAM256 21 903.0 4.5 39.9 141972 93991
   22 Locked QAM256 22 909.0 4.4 39.7 7170844 1977261
   23 Locked QAM256 23 915.0 4.7 39.9 29089566 9859476
   24 Locked QAM256 24 921.0 4.7 39.8 27608222 24894137
   25 Locked QAM256 25 927.0 4.5 39.7 147472 97620
   26 Locked QAM256 26 933.0 4.4 39.6 26976296 19230284
   27 Locked QAM256 27 939.0 4.1 39.3 16596839 2746126
   28 Locked QAM256 28 945.0 4.0 39.4 893268 117118
   29 Locked QAM256 29 951.0 3.8 39.3 445173 115676
   30 Locked QAM256 30 957.0 3.6 39.3 311278 102642
   31 Locked QAM256 31 963.0 3.7 39.3 147216 97185
   32 Locked QAM256 32 969.0 3.8 39.3 147696 106083
   33 Locked OFDM PLC 159 300.0 8.1 42.9 666179889 2134307



   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 19.3 46.3
   2 Locked SC-QAM 2 5120 25.8 46.5
   3 Locked SC-QAM 3 5120 32.2 46.0
   4 Locked SC-QAM 4 5120 38.6 47.3

7

0

B
Bruce

+4 more

Honored Contributor III

 • 

5.7K Messages

It's getting exponentially worst for you, huh?

Are you having problems with connectivity or just concerned about the double-dipping uncorrectables?

Like

Reply

0

B
Bray918

New Contributor III

 • 

42 Messages

Right now I have 14% packetloss at 100.123.66.210, Which is the first hop outside my control. 

Like

Reply

0

B
Bray918

New Contributor III

 • 

42 Messages

The signal is in and out and that is the issue. I'm going to go back to the cm600 tonight and make sure it's not the motorola, but yes, it is dropping connection. Also the correctables are issues for everything on the internet, not just because I don't like to see them. Its causing issues with work logging me out, the kids school, and of course their gaming lag, and videos buffering or poor quality. 

 24 Locked QAM256 39 393.0 14.8 42.9 0 0
   25 Locked QAM256 40 399.0 15.8 43.0 0 0
   26 Locked QAM256 41 405.0 11.1 42.6 0 0

The 300hz and 400hz have been out of spec most of the time I look at the modem, and it doesn't matter which modem.You can tell there is noise on the line by how much power is being used by the modem to overcome the noise to connect to these channels.

Like

Reply

0

J
JonathanJ

Former Moderator

 • 

1.9K Messages

@Bray918

We understand your frustration with this situation and like to take a closer look at the modem's performance levels. Please email me at cox.help@cox.com with your service address and name as this will allow us to locate your Cox account and proceed with having this matter addressed. also include a link to this tread.

Jonathan J
Cox Moderator

Like

Reply

0

B
Bray918

New Contributor III

 • 

42 Messages

I appreciate that and I will take you up on it. But, let me take a few readings on the cm600, I want to make sure the new modem isn't bad. I went back to the sb6141 so I could reboot 500 times to stay off certain channels. I bought the new one to see if I could pull IPV6 to get out ahead of everyone else and alleviate the reboots. It didn't work... LOL

Like

Reply

0

B

Bray918

New Contributor III

 • 

42 Messages

Acquire Downstream Channel 429000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 12h:09m:12s  
  
   Network Access Allowed  
  



   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 45 429.0 3.4 41.0 65380 10357
   2 Locked QAM256 1 783.0 5.3 40.5 43655 24433
   3 Locked QAM256 2 789.0 5.2 40.6 39465 26932
   4 Locked QAM256 3 795.0 5.0 40.6 31645 25557
   5 Locked QAM256 4 801.0 5.1 40.6 25602 20707
   6 Locked QAM256 6 813.0 5.4 40.7 23795 19357
   7 Locked QAM256 7 819.0 5.4 40.8 25013 20279
   8 Locked QAM256 8 825.0 5.6 40.8 1035139 72778
   9 Locked QAM256 10 837.0 5.6 40.8 24533 19058
   10 Locked QAM256 11 843.0 5.5 40.8 23343 16912
   11 Locked QAM256 12 849.0 5.7 40.8 25077 18608
   12 Locked QAM256 13 855.0 5.8 40.8 28282 20490
   13 Locked QAM256 14 861.0 6.1 40.9 31590 19769
   14 Locked QAM256 15 867.0 6.1 40.9 24188 13992
   15 Locked QAM256 20 897.0 5.3 40.5 18998 15150
   16 Locked QAM256 22 909.0 5.4 40.3 21570 14886
   17 Locked QAM256 25 927.0 5.1 40.2 26695 17547
   18 Locked QAM256 33 357.0 4.5 40.9 2263 3355
   19 Locked QAM256 34 363.0 3.0 40.6 2396 3672
   20 Locked QAM256 35 369.0 2.5 40.4 2205 3904
   21 Locked QAM256 36 375.0 2.6 40.5 2708 5091
   22 Locked QAM256 37 381.0 3.5 40.9 3063 5261
   23 Locked QAM256 38 387.0 5.5 41.6 5678 5456
   24 Locked QAM256 39 393.0 9.6 42.5 132003 9024
   25 Locked QAM256 40 399.0 14.3 42.9 78620 45270
   26 Locked QAM256 41 405.0 12.9 42.7 89890 89223
   27 Locked QAM256 42 411.0 8.5 42.2 987494 528314
   28 Locked QAM256 43 417.0 5.6 41.6 42551 44537
   29 Locked QAM256 44 423.0 4.2 41.2 188007 347021
   30 Locked QAM256 46 435.0 3.3 40.9 276922 24078
   31 Locked QAM256 47 441.0 3.8 41.2 77888 10218
   32 Locked QAM256 48 447.0 5.0 41.4 35878 9580
   33 Locked OFDM PLC 159 300.0 8.4 43.7 176471636 136540



   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 19.3 45.8
   2 Locked SC-QAM 2 5120 25.8 45.8
   3 Locked SC-QAM 3 5120 32.2 45.3
   4 Locked SC-QAM 4 5120 38.6 46.3

3

0

B
Bray918

New Contributor III

 • 

42 Messages

Rebooted at 5AM this morning because I was in and out on my internet, wanted to do a little work before I went in. This is what was on there after work.

Like

Reply

0

B
Bray918

New Contributor III

 • 

42 Messages

 Event Log  
  
    Time    Priority    Description 
    18:32:05
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:32:55
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:34:02
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:34:31
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:40:30
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:40:39
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:40:58
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:41:41
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:45:28
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:46:31
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:47:04
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:48:10
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:48:38
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:50:03
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:56:48
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    18:57:18
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:04:35
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:04:45
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 40 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:04:46
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:04:59
Thu Mar 11 2021		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:05:04
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:05:04
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 40 41 42; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:05:04
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 42; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:05:06
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:05:12
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 41 42; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:05:35
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:13:34
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:14:34
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:15:53
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:16:21
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:18:08
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;
    19:18:34
Thu Mar 11 2021		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=00:40:36:73:9e:7c;CMTS-MAC=84:8a:8d:f0:e1:5e;CM-QOS=1.1;CM-VER=3.1;

Like

Reply

0

J
JonathanJ

Former Moderator

 • 

1.9K Messages

@Bray918

The email comes to our social media team and one of us will check the modem signal levels, perform some troubleshooting steps based on our finds and if needed schedule a technician out. When the field technician arrives for the appointment, he or she will inspect the tap that your home connects to, use a meter to check tap components and signal strength, and replace components, if necessary. The tech will then repeat the above procedure at the demarcation point where the coax cable physically enters your home. After inspecting all Cox equipment and cabling outside your home, the tech will test for packet loss and speed issues. Once again the email is cox.help@cox.com.

Jonathan J
Cox Moderator

Like

Reply

0

B

Bray918

New Contributor III

 • 

42 Messages

Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 357000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv4 only
 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 33 357000000 Hz 2.9 dBmV 31.2 dB 0 0
2 Locked QAM256 1 783000000 Hz 3.3 dBmV 39.2 dB 0 0
3 Locked QAM256 2 789000000 Hz 3.2 dBmV 39.2 dB 0 0
4 Locked QAM256 3 795000000 Hz 3.0 dBmV 39.1 dB 0 0
5 Locked QAM256 4 801000000 Hz 3.1 dBmV 39.2 dB 0 0
6 Locked QAM256 5 807000000 Hz 3.5 dBmV 39.4 dB 0 0
7 Locked QAM256 6 813000000 Hz 3.5 dBmV 39.5 dB 0 0
8 Locked QAM256 7 819000000 Hz 3.6 dBmV 39.5 dB 0 0
9 Locked QAM256 8 825000000 Hz 3.8 dBmV 39.7 dB 0 0
10 Locked QAM256 25 927000000 Hz 4.4 dBmV 38.8 dB 0 0
11 Locked QAM256 34 363000000 Hz 1.5 dBmV 30.6 dB 24 0
12 Locked QAM256 35 369000000 Hz 1.1 dBmV 30.5 dB 19 0
13 Locked QAM256 36 375000000 Hz 1.3 dBmV 30.4 dB 22 0
14 Locked QAM256 37 381000000 Hz 2.3 dBmV 30.6 dB 15 0
15 Locked QAM256 38 387000000 Hz 4.0 dBmV 30.7 dB 0 0
16 Locked QAM256 39 393000000 Hz 7.3 dBmV 31.1 dB 17 0
17 Locked QAM256 40 399000000 Hz 10.2 dBmV 31.8 dB 94 0
18 Locked QAM256 41 405000000 Hz 10.4 dBmV 31.3 dB 40 0
19 Locked QAM256 42 411000000 Hz 7.3 dBmV 31.7 dB 0 0
20 Locked QAM256 43 417000000 Hz 4.4 dBmV 31.7 dB 0 0
21 Locked QAM256 45 429000000 Hz 1.5 dBmV 32.1 dB 0 0
22 Locked QAM256 46 435000000 Hz 1.1 dBmV 32.5 dB 0 0
23 Locked QAM256 47 441000000 Hz 1.4 dBmV 33.2 dB 0 0
24 Locked QAM256 48 447000000 Hz 2.0 dBmV 33.7 dB 0 0
 
<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 3 5120 Ksym/sec 32200000 Hz 44.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 19300000 Hz 45.3 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 25800000 Hz 45.3 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 38600000 Hz 45.3 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
Current System Time: Thu Mar 11 19:34:35 2021

1

0

B
Bray918

New Contributor III

 • 

42 Messages

As promised, the CM600. I had heard that the Motorola MB8600 had issues reporting. And heard that the cm600 had issues too, but they both pick up the same issues with the 300 and 400 band. There is a noise issue, and it looks more like a grounding issue at someone's home, 35 years experience in data and communications. If you care to know, I'd go node to node and down from there until I found it, honestly its easy. 

I would say it's an issue they are ignoring because hey, I can give you more speed or a better modem and that will fix most of it but, I just want a solid connection... Each kid at a 150 Mbs connection should be able to game, watch videos on their phones, and second monitor while in a chat with their friends and still have available bandwidth for me to watch a video. I honestly think this is happening for Cox to sell more bandwidth and charge customers for overages...

Whats even better, when they are at their mothers house, I still get buffering, knocked off from work because of drops, if I dont reboot the modem until I get on the right band, its why I switched from 24 channels to "8"! 

Honestly, I can see why cable customers are cutting the cable, I'm trying to get the local TelCo in my area to ask for permits, they are less than a mile away and I'm starting to see a few of my colleagues in the area so, they are thinking about it and they have my data...

My server has been logging all of this and I have my information ready for the next county commissioners meeting. Like I said, I've given up, but I only gave up trying to notify them about issues with their network. It's their network. I'd like to see if another company responds when given the correct data...

Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 429000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv4 only
 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 45 429000000 Hz 4.1 dBmV 38.0 dB 805104 73072
2 Locked QAM256 1 783000000 Hz 2.7 dBmV 38.3 dB 869 69
3 Locked QAM256 2 789000000 Hz 2.7 dBmV 38.4 dB 780 90
4 Locked QAM256 3 795000000 Hz 2.5 dBmV 38.4 dB 819 106
5 Locked QAM256 4 801000000 Hz 2.6 dBmV 38.5 dB 829 109
6 Locked QAM256 33 357000000 Hz 3.8 dBmV 37.7 dB 233318 617
7 Locked QAM256 6 813000000 Hz 3.0 dBmV 38.9 dB 860 112
8 Locked QAM256 7 819000000 Hz 3.0 dBmV 38.9 dB 815 74
9 Locked QAM256 8 825000000 Hz 3.2 dBmV 39.1 dB 710 61
10 Locked QAM256 9 831000000 Hz 3.4 dBmV 39.2 dB 667 30
11 Locked QAM256 34 363000000 Hz 2.9 dBmV 37.2 dB 175743 211
12 Locked QAM256 35 369000000 Hz 2.7 dBmV 37.2 dB 115145 164
13 Locked QAM256 36 375000000 Hz 2.8 dBmV 37.4 dB 152856 199
14 Locked QAM256 37 381000000 Hz 3.2 dBmV 37.6 dB 277455 1064
15 Locked QAM256 38 387000000 Hz 4.0 dBmV 38.4 dB 766425 98685
16 Locked QAM256 39 393000000 Hz 5.5 dBmV 39.4 dB 234458 677
17 Locked QAM256 40 399000000 Hz 6.3 dBmV 40.9 dB 24850 833
18 Locked QAM256 41 405000000 Hz 7.4 dBmV 40.9 dB 35522 6924
19 Locked QAM256 42 411000000 Hz 7.6 dBmV 40.8 dB 34146 16852
20 Locked QAM256 43 417000000 Hz 6.5 dBmV 39.9 dB 35874 3802
21 Locked QAM256 29 951000000 Hz 2.7 dBmV 36.8 dB 0 0
22 Locked QAM256 46 435000000 Hz 2.4 dBmV 37.5 dB 1607 0
23 Locked QAM256 47 441000000 Hz 1.8 dBmV 37.2 dB 555 0
24 Locked QAM256 48 447000000 Hz 1.3 dBmV 36.9 dB 371 0
Help Center Show/Hide Help Ce

Like

Reply

0

B

Bray918

New Contributor III

 • 

42 Messages

Cable Connection
 

3

0

B
Bray918

New Contributor III

 • 

42 Messages

Won't let me document any further?

Like

Reply

0

B
Bray918

New Contributor III

 • 

42 Messages

Acquire Downstream Channel 429000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv4 only
 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 45 429000000 Hz 4.2 dBmV 37.7 dB 805104 73072
2 Locked QAM256 1 783000000 Hz 2.7 dBmV 38.3 dB 869 69
3 Locked QAM256 2 789000000 Hz 2.7 dBmV 38.4 dB 780 90
4 Locked QAM256 3 795000000 Hz 2.5 dBmV 38.3 dB 819 106
5 Locked QAM256 4 801000000 Hz 2.6 dBmV 38.4 dB 829 109
6 Locked QAM256 33 357000000 Hz 3.9 dBmV 37.3 dB 233318 617
7 Locked QAM256 6 813000000 Hz 3.0 dBmV 38.8 dB 860 112
8 Locked QAM256 7 819000000 Hz 3.0 dBmV 38.8 dB 815 74
9 Locked QAM256 8 825000000 Hz 3.2 dBmV 39.0 dB 710 61
10 Locked QAM256 9 831000000 Hz 3.4 dBmV 39.2 dB 667 30
11 Locked QAM256 34 363000000 Hz 3.1 dBmV 37.0 dB 175743 211
12 Locked QAM256 35 369000000 Hz 2.9 dBmV 37.0 dB 115145 164
13 Locked QAM256 36 375000000 Hz 3.0 dBmV 37.2 dB 152856 199
14 Locked QAM256 37 381000000 Hz 3.4 dBmV 37.6 dB 277455 1064
15 Locked QAM256 38 387000000 Hz 4.1 dBmV 38.4 dB 766425 98685
16 Locked QAM256 39 393000000 Hz 5.5 dBmV 39.3 dB 234458 677
17 Locked QAM256 40 399000000 Hz 6.2 dBmV 40.3 dB 24850 833
18 Locked QAM256 41 405000000 Hz 7.2 dBmV 40.4 dB 35522 6924
19 Locked QAM256 42 411000000 Hz 7.4 dBmV 40.3 dB 34146 16852
20 Locked QAM256 43 417000000 Hz 6.5 dBmV 39.4 dB 35874 3802
21 Locked QAM256 29 951000000 Hz 2.8 dBmV 36.8 dB 0 0
22 Locked QAM256 46 435000000 Hz 2.5 dBmV 36.8 dB 1607 0
23 Locked QAM256 47 441000000 Hz 1.8 dBmV 36.7 dB 555 0
24 Locked QAM256 48 447000000 Hz 1.3 dBmV 36.5 dB 371 0
 
<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 3 5120 Ksym/sec 32200000 Hz 43.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 19300000 Hz 45.0 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 25800000 Hz 45.0 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 38600000 Hz 45.0 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
Current System Time: Thu Mar 11 20:45:16 2021
System Up Time: 1:15:58

Like

Reply

0

B
Bray918

New Contributor III

 • 

42 Messages

They don't do tickets so you can track the issue, so for me posting on here is my ticket.

That's an hour. I'll let it run 24hrs then I'll post again, then I'll place a call. I appreciate you all for looking, I'm just tired of dealing with it, and I hope none of you are going through this.

Like

Reply

0

D

Dave9

Contributor III

 • 

251 Messages

The large number of uncorrectables on all channels combined with the rapid cycles of event ID 16 and event ID 24 indicate wideband noise ingress on the line or a failure of a device such as an amplifier. It is definitely not normal. If you have tightened all connections and replaced all interior cables with brand new high quality RG6 cable your only option is to call for a tech.

0

0

Recent Discussions