Forum Discussion

Rigbly1's avatar
Rigbly1
New Contributor
5 years ago

Upstream SNR

COX says 35.0 dBmV upstream SNR is within the range of acceptable

Arris says the correct bonded upstream snr for the internet to stop dropping is 45-51 DBmV

Why can I not get COX to raise the SNR to what I need to have the internet stop dropping?

Downstream is great. No issues there. Also I have PAGES of this

05/19/2020 09:16 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 09:15 74010100 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=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 07:37 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 07:36 74010100 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=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 03:53 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 03:53 74010100 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=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 02:04 2436694061 5 "Dynamic Range Window violation"
05/19/2020 02:04 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"
05/19/2020 02:04 2436694061 5 "Dynamic Range Window violation"
05/19/2020 02:04 82001200 5 "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=a4:98:13:fa:16:1d;CMTS-MAC=00:bc:60:92:de:42;CM-QOS=1.1;CM-VER=3.1;"

Can someone who knows something please let me know what the issue is?

Gigablast Issues SB8200
  • Dave9's avatar
    Dave9
    Contributor III
    5 years ago

    This is a personal opinion only, but I think the upstream power levels specified by Arris might not be applicable. The upstream power determines how "loud" your modem has to talk in order to send data on the internet. (Really this means sending data to the Cox node but I'm oversimplifying). If the Cox node isn't receiving your modem clearly, it can ask the modem to "talk louder" which means increasing the upstream power. If your upstream power is lower than expected, that could mean that node can receive your modem without needing a lot of power and that can mean you have a very good connection. So my personal feeling is that a lower upstream power can be fine. But if the upstream power is too high it indicates a problem. Maybe someone with more technical knowledge can offer a better explanation.

  • Bruce's avatar
    Bruce
    Honored Contributor III
    5 years ago

    I think you're asking about power because SNR is measured in decibels (dB)...not dBmV.  Power is measured in dBmV.

    There are ranges within operational specs:  Best, Good, Operational and Out-of-Specs.  Arris gave you the Best range.  However, since Cox designed the network, only Cox can provide the Best range...albeit, 45-51 dBmV sounds great.

    35 dBmV appears kinda low and could result in packet loss...then again, only Cox can provide acceptable signal strengths.  Allan provided your cause so perhaps a Best range is coming soon.

  • Allan's avatar
    Allan
    Moderator
    5 years ago
    @Rigbly1, It looks like we are currently conducting upgrades in your area. We have been notifying our customers through door hangers. Also, you can get updates during this upgrade with our Cox app. Once completed, you should no longer be experiencing issues with the service. -Allan, Cox Support Forums Moderator.