Skip to main content
Golden's profile

Golden

New Contributor

 • 

4 Messages

Closed

Do my signals look good? I suspect I have a problem.

Do my signals look good? I suspect I have a problem.

I live in a townhome. Built about 5 years ago. I've installed a MoCA POE filter outside. I don't have pre-filter results.

I had problems installing my MoCA, so I ditched that and right now I'm using 4 eero Pros via ethernet (using a switch at the media closet/cabinet).

I have Cox Gigablast. My eero speed test says 930 Mbps down. However, my eero Pros are each only getting ~122 Mbps down (when only my device is being used).

 Startup Sequence    
   Startup Step Status Comment

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

  
   Configuration File OK
  
   Security Enabled BPI+
  



   Connection Status    
   System Up Time 0 days 04h:55m: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 843.0 -12.1 37.0 548 548
   2 Locked QAM256 1 675.0 -12.0 36.8 0 0
   3 Locked QAM256 2 681.0 -12.0 37.6 0 0
   4 Locked QAM256 3 687.0 -12.0 37.4 0 0
   5 Locked QAM256 4 693.0 -11.8 37.7 0 0
   6 Locked QAM256 5 699.0 -12.0 37.4 0 0
   7 Locked QAM256 6 705.0 -11.8 37.5 0 0
   8 Locked QAM256 7 711.0 -11.8 37.6 0 0
   9 Locked QAM256 8 717.0 -12.0 37.3 0 0
   10 Locked QAM256 9 723.0 -11.8 37.6 0 0
   11 Locked QAM256 10 729.0 -11.7 35.8 0 0
   12 Locked QAM256 11 735.0 -11.4 36.3 16961958 1476820
   13 Locked QAM256 12 741.0 -11.2 26.3 63897413 117573043
   14 Locked QAM256 13 747.0 -11.3 37.6 0 0
   15 Locked QAM256 14 753.0 -11.2 37.4 0 0
   16 Locked QAM256 15 759.0 -11.5 36.2 1971952 489123
   17 Locked QAM256 16 765.0 -11.8 35.0 1457284 734661
   18 Locked QAM256 17 771.0 -12.2 36.8 0 0
   19 Locked QAM256 18 777.0 -13.3 36.1 0 0
   20 Locked QAM256 19 783.0 -14.1 35.7 0 0
   21 Locked QAM256 20 789.0 -15.3 34.7 0 0
   22 Locked QAM256 21 795.0 -15.9 34.2 0 0
   23 Locked QAM256 22 801.0 -15.1 34.9 0 0
   24 Locked QAM256 23 807.0 -14.4 35.5 0 0
   25 Locked QAM256 24 813.0 -13.3 36.2 0 0
   26 Locked QAM256 25 819.0 -13.0 36.4 0 0
   27 Locked QAM256 26 825.0 -12.8 36.6 0 0
   28 Locked QAM256 27 831.0 -12.3 36.9 0 0
   29 Locked QAM256 28 837.0 -12.5 36.7 306 34
   30 Locked QAM256 30 849.0 -11.6 37.5 0 0
   31 Locked QAM256 31 855.0 -11.8 37.3 0 0
   32 Locked QAM256 32 861.0 -11.2 35.3 0 0
   33 Locked OFDM PLC 159 288.0 -3.7 15.9 91850893 0



   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 17.4 43.3
   2 Locked SC-QAM 2 5120 23.9 44.3
   3 Locked SC-QAM 3 5120 30.3 44.8
   4 Locked SC-QAM 4 5120 36.7 45.8

Discussions

 • 

Updated 

1.5K

4

0

0

G

Golden

New Contributor

 • 

4 Messages

Event Log
   Log  
  
    Time    Priority    Description 
    23:00:09
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:00:10
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:00:50
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:00:51
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:00:55
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:02:50
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:02:51
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:02:55
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:04:20
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:04:21
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:04:23
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:05:26
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:05:27
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:05:28
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:07:46
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:07:47
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:07:49
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:15:38
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:15:39
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:15:43
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:19:00
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:19:01
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:19:03
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:32:09
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:32:09
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:32:11
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:33:27
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:33:27
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:33:29
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:38:59
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:38:59
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:39:03
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;

0

0

F

FatDaddyWampus

Contributor

 • 

42 Messages

Your downstream levels are too low.  Ideally, you'd want 0dBmV +-5 and all channels within 5dBmV of each other.  I'm also surprised your upstream isn't higher than it is.

2

G
Golden

New Contributor

 • 

4 Messages

Thank you for responding. Do I just call Cox? Is this a problem with my townhome or the Cox infrastructure? It sounds like this is something they send someone out for?

Like

Reply

0

F
FatDaddyWampus

Contributor

 • 

42 Messages

If you can access your DMarc, I'd get in there and disconnect everything that isn't being used OR if possible, just bypass everything and connect from Cox's cable (the one from the street to your DMarc) to your modem with as little connections as possible and see what your levels look like.  As a reference, when I bypass everything in my DMarc and just have 2 pieces of coax between my modem and the street, my levels are about 10dBmv, but that's not optimal so I put in a 2 way splitter to attenuate it down.

Also, if you decide to run your own cable for troublshooting, make sure it's quality RG6.

Keep it mind, it's Cox's stance with everything wrong with their service to blame the end user, so if you can bypass everything from the DMarc to your modem with new cabling, it will give you better ammo to put the blame back on them.

Also, FYI, the cable from the street to your DMarc is their cable and they should replace it if it's bad.  Doing so yourself could cause more problems in the long run, because it's a direct burial cable designed to withstand water that will build up in the conduit it's pulled through.

Like

Reply

0

G

Golden

New Contributor

 • 

4 Messages

Event Log
   Log  
  
    Time    Priority    Description 
    23:00:09
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:00:10
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:00:50
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:00:51
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:00:55
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:02:50
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:02:51
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:02:55
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:04:20
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:04:21
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:04:23
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:05:26
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:05:27
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:05:28
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:07:46
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:07:47
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:07:49
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:15:38
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:15:39
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:15:43
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:19:00
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:19:01
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:19:03
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:32:09
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:32:09
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:32:11
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:33:27
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:33:27
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:33:29
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:38:59
Tue Aug 18 2020		   Warning (5)   MDD message timeout;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:38:59
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;
    23:39:03
Tue Aug 18 2020		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:4e:d4:ac;CMTS-MAC=00:d6:fe:e7:a5:5c;CM-QOS=1.1;CM-VER=3.1;

1

0

D
Dave9

Contributor III

 • 

251 Messages

Everything in there refers to MDD messages, even the CM-STATUS event codes relate to MDD. Combine that with the error counts and you might have a downstream noise issue. If all of your indoor cables are new and tightly connected you would need a Cox tech to fix it.

Like

Reply

0

D

Dave9

Contributor III

 • 

251 Messages

Signal levels are too low and looks like you have major LTE ingress on channels 12, 13, 16, and 17. Look at the huge number of errors on those channels compared to the zeros on other channels. Tighten interior cable connections and replace interior cables with good quality RG6 cable. If that doesn't help there might be a problem outside your home that's letting cellular signals into the network and causing interference. If that's the case you'd need a Cox tech to investigate and repair.

0

0