- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
CM1200 intermittently dropping internet connection
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CM1200 intermittently dropping internet connection
Hello Gurus,
For the past three days my CM1200 has been dropping it's internet connection multiple times throughout the day. It was so bad yesterday, that I contacted my ISP (Cox Communications) multiple times during the day. They would have me do a manual reset or they would send a signal to the modem and reset it that way. I finally got a representative to agree to send a line tech out after the fifth call. The line tech will be here tomorrow morning and my internet drops seem worst today. What I have noticed is that the downstream light on the modem would be flashing when I would lose my internet connection. Today, I have noticed that the modem has been resetting (All lights are dark except power), then it takes a moment to establish it's connection.
There are no splitters. The cable runs right from the wall directly to the modem, which I have an ASUS RT-AX88U router connected to it. I want to make sure my modem is ok before the line tech arrives tomorrow. Thank you.
Here is the current log:
Time | Priority | Description |
Wed Jun 15 14:43:54 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:43:50 2022 | Warning (5) | MDD message timeout;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:43:46 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:42:46 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 13 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:42:43 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 5 13 18 19 20 22 25 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:42:42 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 18 19 20 22 25 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:42:41 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:42:24 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:42:22 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:42:20 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18 19 20 22 25 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:42:18 2022 | Warning (5) | MDD message timeout;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:40:06 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 5 13 18 22 25 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:40:02 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 13 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:40:00 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 18 22 25 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:39:54 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18 22 25 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:39:53 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:38:55 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:38:49 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:38:44 2022 | Warning (5) | MDD message timeout;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:38:06 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:38:01 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:37:56 2022 | Warning (5) | MDD message timeout;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:37:54 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:37:54 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 18 22 25 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:37:53 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:37:53 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:37:27 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:37:27 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:36:51 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:36:45 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:36:25 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 5 13 18 22 25 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:36:23 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:36:19 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 5 13 18 22 25 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:36:12 2022 | Warning (5) | MDD message timeout;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:36:07 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 5 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:35:59 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:35:58 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:35:58 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:21:19 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 15 14:21:18 2022 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=38:94:ed:08:8d:48;CMTS-MAC=cc:8e:71:68:75:5c;CM-QOS=1.1;CM-VER=3.1; |
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more