Forum Discussion

Dave9's avatar
Dave9
Contributor III
4 years ago

900 MHz ingress started about 2 hours ago

Ingress on 900 MHz channels started about 2 hours ago and continues unabated with thousands of uncorrectables per hour only on channels 21-25 as you see below. Causing glitches on video calls. See signals and event logs below. Can this be directly escalated to a plant ticket? It would be a waste of time to send a tech. It's not my equipment.

EDIT: As you can see this lines up perfectly with the 902-928 MHz unlicensed band. Someone on my node must have set up a new 900 MHz device near some leaky coax. I have nothing in my home that runs on this band and I did not introduce any new wireless devices today. I hope Cox monitors for this type of thing since my neighbors won't know to report this. They'll just blame their equipment or blame Cox when this is clearly an ingress issue.

Date Time Event ID Event Level Description
08/24/2020 12:04 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=(redacted);CMTS-MAC=(redacted);CM-QOS=1.1;CM-VER=3.1;"
08/24/2020 12:04 84020300 5 "MDD message timeout;CM-MAC=(redacted);CMTS-MAC=(redacted);CM-QOS=1.1;CM-VER=3.1;"
08/24/2020 12:00 74010100 6 "CM-STATUS message sent. Event Type Code: 5; Chan ID: 22 23 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=(redacted);CMTS-MAC=(redacted);CM-QOS=1.1;CM-VER=3.1;"
08/24/2020 12:00 74010100 6 "CM-STATUS message sent. Event Type Code: 2; Chan ID: 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=(redacted);CMTS-MAC=(redacted);CM-QOS=1.1;CM-VER=3.1;"
08/24/2020 11:57 74010100 6 "CM-STATUS message sent. Event Type Code: 5; Chan ID: 22 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=(redacted);CMTS-MAC=(redacted);CM-QOS=1.1;CM-VER=3.1;"
08/24/2020 11:57 74010100 6 "CM-STATUS message sent. Event Type Code: 2; Chan ID: 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=(redacted);CMTS-MAC=(redacted);CM-QOS=1.1;CM-VER=3.1;"
08/24/2020 11:04 74010100 6 "CM-STATUS message sent. Event Type Code: 5; Chan ID: 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=(redacted);CMTS-MAC=(redacted);CM-QOS=1.1;CM-VER=3.1;"
08/24/2020 11:04 74010100 6

"CM-STATUS message sent. Event Type Code: 2; Chan ID: 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=(redacted);CMTS-MAC=(redacted);CM-QOS=1.1;CM-VER=3.1;"

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
5 Locked QAM256 807000000 Hz 6.0 dBmV 43.0 dB 2 0
1 Locked QAM256 783000000 Hz 6.5 dBmV 43.2 dB 1 0
2 Locked QAM256 789000000 Hz 6.7 dBmV 43.3 dB 0 0
3 Locked QAM256 795000000 Hz 6.2 dBmV 43.0 dB 0 0
4 Locked QAM256 801000000 Hz 6.3 dBmV 42.8 dB 2 0
6 Locked QAM256 813000000 Hz 5.7 dBmV 42.8 dB 4 0
7 Locked QAM256 819000000 Hz 5.8 dBmV 42.8 dB 3 0
8 Locked QAM256 825000000 Hz 5.3 dBmV 42.4 dB 2 0
9 Locked QAM256 831000000 Hz 5.4 dBmV 42.6 dB 3 0
10 Locked QAM256 837000000 Hz 5.1 dBmV 42.4 dB 3 0
11 Locked QAM256 843000000 Hz 5.0 dBmV 42.4 dB 1 0
12 Locked QAM256 849000000 Hz 5.0 dBmV 42.3 dB 5 0
13 Locked QAM256 855000000 Hz 4.6 dBmV 42.2 dB 5 0
14 Locked QAM256 861000000 Hz 4.6 dBmV 41.4 dB 3 0
15 Locked QAM256 867000000 Hz 4.2 dBmV 41.6 dB 5 0
16 Locked QAM256 873000000 Hz 4.0 dBmV 41.7 dB 6 0
17 Locked QAM256 879000000 Hz 4.1 dBmV 41.8 dB 2 0
18 Locked QAM256 885000000 Hz 3.7 dBmV 41.5 dB 3 0
19 Locked QAM256 891000000 Hz 3.6 dBmV 41.6 dB 3 0
20 Locked QAM256 897000000 Hz 3.4 dBmV 41.5 dB 1 0
21 Locked QAM256 903000000 Hz 3.3 dBmV 41.5 dB 15579 2956
22 Locked QAM256 909000000 Hz 3.4 dBmV 41.4 dB 11536 31968
23 Locked QAM256 915000000 Hz 3.2 dBmV 41.4 dB 1418 7321
24 Locked QAM256 921000000 Hz 3.3 dBmV 41.5 dB 7736 11308
25 Locked QAM256 927000000 Hz 3.1 dBmV 41.3 dB 5548 944
26 Locked QAM256 933000000 Hz 2.8 dBmV 41.2 dB 2 0
27 Locked QAM256 939000000 Hz 2.8 dBmV 41.1 dB 1 0
28 Locked QAM256 945000000 Hz 2.7 dBmV 41.1 dB 1 0
29 Locked QAM256 951000000 Hz 2.5 dBmV 41.1 dB 0 0
30 Locked QAM256 957000000 Hz 2.5 dBmV 41.2 dB 0 0
31 Locked QAM256 963000000 Hz 2.2 dBmV 41.1 dB 0 0
32 Locked QAM256 969000000 Hz 2.5 dBmV 41.4 dB 0 0
159 Locked Other 300000000 Hz 3.0 dBmV 42.0 dB 153833195 0



Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 2 Locked SC-QAM Upstream 23500000 Hz 6400000 Hz 38.0 dBmV
2 1 Locked SC-QAM Upstream 16900000 Hz 6400000 Hz 38.0 dBmV
3 3 Locked SC-QAM Upstream 29900000 Hz 6400000 Hz 39.0 dBmV
4 4 Locked SC-QAM Upstream 36300000 Hz 6400000 Hz 40.0 dBmV

2 Replies

  • Dave9's avatar
    Dave9
    Contributor III

    The problem appears have to subsided as of a couple of hours ago. Hopefully the problem has been resolved and it's not just that the offending device was powered off for the evening.

    • Dave9's avatar
      Dave9
      Contributor III

      Ingress has started again at just about the same time as yesterday. Someone must be turning on a 900 MHz unlicensed wireless device that's putting noise on the line. Please investigate. Modem was reset last night to clear the counters. I had 0 uncorrectables on any channel all night and most of the morning. I can't wait for fiber when my connection can't be affected by defective devices in my neighbors' homes.

      20 Locked QAM256 897000000 Hz 3.5 dBmV 41.9 dB 5 0
      21 Locked QAM256 903000000 Hz 3.4 dBmV 41.9 dB 36 0
      22 Locked QAM256 909000000 Hz 3.4 dBmV 42.0 dB 5570 4093
      23 Locked QAM256 915000000 Hz 3.2 dBmV 41.8 dB 4664 12254
      24 Locked QAM256 921000000 Hz 3.3 dBmV 41.9 dB 7400 13918
      25 Locked QAM256 927000000 Hz 3.0 dBmV 41.3 dB 159 1
      26 Locked QAM256 933000000 Hz 2.7 dBmV 41.5 dB 2 0