New Poster
•
1 Message
Internet degrades when it is windy and rainy
For the last few weeks, my internet was getting worse and worse. It was dropping out for 40 seconds to up to 9 minutes, every hour or so. Unfortunately, I had a dual problem, I think...
1) my modem was bad. I had the infamous Arris SB8200. I replaced it with a Netgear CM1000 and things got much, much better. I had one day of flawless performance.
2) And then it got windy and rainy, and my error logs filled up with thousands of uncorrectable code words on every channel, plus Dynamic Range Window violations, T3 time-outs, and CM-STATUS message sent: Event Type Code: 24, 16, and 8.
Below are two days worth of status and error logs. What's the best way to attract attention on this issue and get a tech to check things out? I've been a customer for less than a year, and the drop from the street to the house is new with the service, and goes straight into the modem upon entering the house. However, the neighborhood is old and so is the wiring on the street...
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Current System Time: Mon Oct 19 20:25:48 2020 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| System Up Time: 61:29:15 |
| Time | Priority | Description |
| 2020-10-19, 19:53:20 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:52:51 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:41:32 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:40:06 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:39:58 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:38:47 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:38:37 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:38:09 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:31:30 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:30:59 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:25:27 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 19:24:35 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:49:43 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:49:12 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:48:38 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:48:17 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:47:02 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:46:13 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:45:48 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:44:15 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:42:15 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:41:46 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:24:20 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:23:49 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:22:23 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 18:21:15 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:20:06 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:07:17 | Warning (5) | Dynamic Range Window violation |
| 2020-10-19, 17:07:17 | Warning (5) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:05:37 | Notice (6) | CM-STATUS message sent. Event Type Code: 8; Chan ID: 1 2 4 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:04:57 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:04:53 | Notice (6) | CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:04:51 | Warning (5) | Dynamic Range Window violation |
| 2020-10-19, 17:04:51 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:04:51 | Warning (5) | Dynamic Range Window violation |
| 2020-10-19, 17:04:51 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:04:51 | Warning (5) | Dynamic Range Window violation |
| 2020-10-19, 17:04:51 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:04:40 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
| 2020-10-19, 17:04:40 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=44:a5:6e:b7:3c:60;CMTS-MAC=00:01:5c:b3:b2:6a;CM-QOS=1.1;CM-VER=3.1; |
Finally, here are the outage logs from the connection monitoring software installed when things were bad:
Oct 19 6:04:56 PM
Network Up. Outage lasted 92 seconds.
7 tests failed during the outage.
Oct 19 6:03:23 PM
Connection Outage Detected
Oct 19 1:54:54 PM
Network Up. Outage lasted 53 seconds.
5 tests failed during the outage.
Oct 19 1:54:00 PM
Connection Outage Detected
Oct 18 5:01:40 PM
Network Up. Outage lasted 36 seconds.
4 tests failed during the outage.
Oct 18 5:01:40 PM
DNS is back online.
Oct 18 5:01:04 PM
DNS Outage Detected - URL Domain Names are not being resolved to IP addresses by the DNS Server your Internet connection is using, but IP address based traffic is still flowing over the connection. Check your local DNS settings or the DNS server they point to.
Oct 17 8:04:19 AM
Connection Online
Oct 17 8:04:19 AM
Internet Connection Testing Started
Responses
No Responses!