Contributor
•
286 Messages
Coda56 modem goes "offline" periodically around the time get "REG-RSP-MP Mismatch" errors
I've been dealing with an issue that I believe is a Comcast signal issue that is causing my modem to lock up. I have a Hitron Code56 which I got on November 25, 2023 to replace an Arris S33 as that doesn't support the faster upload speeds.
Since Jan 7, I've had the Coda56 "lock up" where the lights on it remain solid, but I can't get any WAN traffic until I reset or power cycle the modem. During that time Comcast's Xfinity app reports the modem is offline. I can still pull logs off it by directly hitting the asp endpoints, though its web page UI doesn't load properly in this state. I've waited as long as 10 minutes for the modem to recover and it never does.
When not locking up the modem works great. I get the 800+/100+ speeds I pay for. I don't get any packet loss and the ping times are mostly low. Basically the modem works great until it just goes offline.
So far this has happened 3 times: Jan 7, Feb 2 and Feb 8. Around the days this happened I saw the following errors in the logs:
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
These errors only show up once a day or any time I reset the modem. I saw about one a month in Nov and Dec of 2023. I saw several in January and this month (Feb), I've seen them every few days. Any day the modem locks up I've seen them, but the modem doesn't lock up every day they appear. In addition I a T3 error every hour or so. I get around a few dozen corrected errors a day, but usually no uncorrected ones (maybe 2 or 3 on an off day).
Despite the errors, the modem's signals as reported are good. I've confirmed that the modem downstream and upstream transmit power matches what Comcast's Reddit support team sees. They told me all my signals are in spec with the exception of the received upstream power level which they said is 18.25 dbMV. They said the receiver should be -2 to 2.
As my upstream transmit power is about 39 (+-1) for the QAM64 channels and 41 for the OFDMA channel (Comcast says it's 44.5 for some reason). The entire power level is reported as 55 dBmV which seems high. I've read that the dynamic range window (DRW) can't be greater than 12 dBmV, so I'm not sure how 55 would work, but 44.5 would.
I've had a tech out today who said my signals are good, which again ignoring the receive power levels, they are. Reaching out to Comcast support seems pointless as when I told them the tech said the signals were good, but I'm still seeing errors in the logs, they asked if I wanted another tech sent out. Techs are not RF engineers and can only go by what their meters tell them, so they don't see things like receive power levels or the like.
I've also reached out to Hitron who just said the modem is under warranty and wants me to send it back to them for replacement. I'm not convinced the modem is defective though.
Any ideas on what's wrong and how to solve it?
The modem's logs are in JSON, so I wrote a script to read and parse them to make them more compact, which is why they look odd, but basically "Str" is the power, "C" is corrected errors and "U" is uncorrected errors, cBw is channelBw, da is "digAtten" and daBo is "digAttenBo". Frequency is in Mhz.
Here's the signals (I rebooted it today):
Downstream:
{"P":1,"Freq":567,"Str":1.000,"SNR":40.366,"C":23,"U":26}
{"P":2,"Freq":615,"Str":0.200,"SNR":40.366,"C":2,"U":0}
{"P":3,"Freq":663,"Str":1.200,"SNR":40.946,"C":1,"U":0}
{"P":4,"Freq":711,"Str":0.700,"SNR":40.366,"C":0,"U":0}
{"P":5,"Freq":525,"Str":2.100,"SNR":40.946,"C":9,"U":0}
{"P":6,"Freq":531,"Str":1.700,"SNR":40.946,"C":16,"U":0}
{"P":7,"Freq":537,"Str":1.700,"SNR":40.946,"C":3,"U":0}
{"P":8,"Freq":543,"Str":1.700,"SNR":40.946,"C":4,"U":0}
{"P":9,"Freq":549,"Str":1.300,"SNR":40.366,"C":20,"U":0}
{"P":10,"Freq":555,"Str":1.200,"SNR":40.366,"C":13,"U":0}
{"P":11,"Freq":561,"Str":1.300,"SNR":40.946,"C":11,"U":0}
{"P":12,"Freq":573,"Str":0.900,"SNR":40.366,"C":8,"U":0}
{"P":13,"Freq":579,"Str":0.800,"SNR":40.366,"C":11,"U":0}
{"P":14,"Freq":585,"Str":0.800,"SNR":40.946,"C":12,"U":0}
{"P":15,"Freq":591,"Str":0.500,"SNR":40.366,"C":0,"U":0}
{"P":16,"Freq":597,"Str":0.500,"SNR":40.946,"C":5,"U":0}
{"P":17,"Freq":603,"Str":0.600,"SNR":40.946,"C":2,"U":0}
{"P":18,"Freq":609,"Str":0.200,"SNR":40.366,"C":1,"U":0}
{"P":19,"Freq":621,"Str":0.800,"SNR":40.366,"C":1,"U":0}
{"P":20,"Freq":627,"Str":0.400,"SNR":40.366,"C":1,"U":0}
{"P":21,"Freq":633,"Str":0.500,"SNR":40.366,"C":3,"U":0}
{"P":22,"Freq":639,"Str":0.700,"SNR":40.946,"C":1,"U":0}
{"P":23,"Freq":645,"Str":0.700,"SNR":40.366,"C":2,"U":0}
{"P":24,"Freq":651,"Str":1.000,"SNR":40.946,"C":6,"U":0}
{"P":25,"Freq":657,"Str":1.200,"SNR":40.946,"C":0,"U":0}
{"P":26,"Freq":669,"Str":1.200,"SNR":40.366,"C":1,"U":0}
{"P":27,"Freq":675,"Str":1.100,"SNR":40.946,"C":1,"U":0}
{"P":28,"Freq":681,"Str":0.900,"SNR":40.366,"C":0,"U":0}
{"P":29,"Freq":687,"Str":1.200,"SNR":40.366,"C":0,"U":0}
{"P":30,"Freq":693,"Str":0.900,"SNR":40.366,"C":2,"U":0}
{"P":31,"Freq":699,"Str":0.900,"SNR":40.366,"C":0,"U":0}
{"P":32,"Freq":705,"Str":0.900,"SNR":40.366,"C":0,"U":0}
Downstream OFDM:
{"Freq":803.6,"Str":0.400002,"SNR":40,"U":0}
Upstream:
{"P":1,"Freq":29.2,"Mod":"64QAM","SM":"ATDMA","Str":38.500}
{"P":2,"Freq":35.6,"Mod":"64QAM","SM":"ATDMA","Str":39.000}
{"P":3,"Freq":16.4,"Mod":"64QAM","SM":"ATDMA","Str":38.000}
{"P":4,"Freq":22.8,"Mod":"64QAM","SM":"ATDMA","Str":38.250}
Upstream OFDM:
{"Freq":36.2,"da":0.1643,"daBo":6.1260,"cBW":44.4000,"Pow":55.4326,"Pow1_6":41.0000}
Here's the current logs. Note tech was here disconnecting cable around 10:45 to 11 am and I reset the modem on Feb 8 after it locked up:
{"T":"02/09/24 15:18:10","E":"No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:13:51","E":"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:13:50","E":"REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:13:46","E":"MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"12/31/69 19:01:07","E":"CM-STATUS message sent. CMSTATUS: DS_Diplexer_Mode_Change:[band1][108-1002Mhz];CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:12:01","E":"CM Reboot Reason : SNMP_RESET;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:08:44","E":"CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:06:55","E":"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:06:43","E":"CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:06:26","E":"Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:06:23","E":"CM-STATUS message sent. Event Type Code: 21; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 11:06:21","E":"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:54:13","E":"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:54:13","E":"REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:54:11","E":"MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:53:47","E":"Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:52:01","E":"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:51:12","E":"Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:51:09","E":"CM-STATUS message sent. Event Type Code: 21; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:51:09","E":"Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:34:22","E":"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:34:22","E":"REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:34:20","E":"MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:33:56","E":"Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:31:19","E":"Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:30:29","E":"Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:30:28","E":"CM-STATUS message sent. Event Type Code: 21; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 10:30:22","E":"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 08:02:31","E":"No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 04:47:29","E":"CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 04:47:13","E":"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 04:47:11","E":"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/09/24 00:00:02","E":"No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 14:32:34","E":"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 14:32:34","E":"REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 14:32:30","E":"MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"12/31/69 19:01:07","E":"CM-STATUS message sent. CMSTATUS: DS_Diplexer_Mode_Change:[band1][108-1002Mhz];CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"12/31/69 19:01:04","E":"CM Reboot Reason : POWER_ON;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 11:11:20","E":"No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 07:56:16","E":"US profile assignment change. US Chan ID: 41; Previous Profile: 11; New Profile: 12.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 07:56:16","E":"US profile assignment change. US Chan ID: 41; Previous Profile: 11; New Profile: 12.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 07:55:04","E":"No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 07:50:31","E":"US profile assignment change. US Chan ID: 41; Previous Profile: 12; New Profile: 11.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 07:08:19","E":"No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 05:19:05","E":"DS profile config update. DS Chan ID: 193.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/08/24 05:16:23","E":"No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/06/24 05:18:44","E":"DS profile config update. DS Chan ID: 193.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/06/24 04:57:31","E":"US profile assignment change. US Chan ID: 41; Previous Profile: 11; New Profile: 12.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/06/24 04:46:00","E":"US profile config update. US Chan ID: 41.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/06/24 03:36:54","E":"No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/06/24 02:54:37","E":"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/06/24 02:54:37","E":"REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
{"T":"02/06/24 02:54:34","E":"MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"}
Morac2
Contributor
•
286 Messages
1 year ago
This should be easier to read.
0
0
Morac2
Contributor
•
286 Messages
1 year ago
So I decided to take up Hitron and send back the Coda56 and hooked my S3 back up. The signals it reports are completely different. They appear better but after watching https://www.youtube.com/live/CJAKmQ2u7pk which mentioned that Docsis 3.1 reports transmit power differently, that the S33 is probably reporting as P6.4 (46), while the Coda56 is reporting as P1.6 (38) meaning they are the same. That doesn’t explain the errors on the Coda56 or why it locks up periodically unless that’s something OFDMA upstream specific as the Coda56 support OFDMA upstream while the S33 does not.
The S33 has better downstream signals and SNR though and doesn’t generate those T3 or RNG RSP errors.
0
0
user_po32d0
1 Message
1 year ago
I am having a similar issue after upgrading to a Coda56 modem - repeated lockups at random times and needed to power cycle modem to get a connection, modem would work for 10 to 15 minutes and then it would lock up again... this would repeat for an hour or so and then everything would work fine for a few weeks (or sometimes days) - today the Coda56 has been freaking out for 6 hours...
the coda56 up/down signal report looks relatively similar to what you've posted above, although my downstream signal strength is 2.6 to 4.3 dBmV across all ports...
I've just replaced the Coda56 with a surfboard8200 (the modem I had replaced) to see if it everything stabilizes so I can get some actual work done today
thank you for documenting what you've seen - it was a huge help to realize that my issues might be due to the coda56...
0
0