Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Need assistance decoding CM1000 logs please!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2020-05-14
11:36 AM
2020-05-14
11:36 AM
Need assistance decoding CM1000 logs please!
Good afternoon... for some reason, my posts keep getting deleted/rejected. Not sure why. 😞 I am having issues maintaining a solid internet connection on a CM1000 wiht XFinity cable, and drops intermittently throughout the day. Could you please take a look at these logs below, and let me know if in your opinion, this is an XFinity line connectivity/upstream issue, or if this is typical behavior of one of these units going back? It's much appreciated!
Here are some events from 5/11:
2020-05-11, 12:01:46 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 12:00: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: 1 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 12:00:30 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 12:00:16 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6 Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:54:16 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:43:53 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:43:50 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:43:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:43:36 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:43:34 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:43:07 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:42:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-11, 11:42:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1;
Here are some events from 5/14:
2020-05-14, 10:42:54 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:42:46 Notice (6) Honoring MDD; IP provisioning mode = IPv6 2020-05-14, 10:41:35 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:41:29 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:41:28 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:41:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:41:11 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:40:47 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:40:47 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:40:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:40:34 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:40:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:40:22 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:40:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:40:10 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:39:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:39:51 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:39:03 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:39:02 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:38:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:38:38 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:38:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:38:32 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:38:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:38:25 Notice (6) CM-STATUS message sent. Event Type Code: 21; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:38:24 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:38:24 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:37:05 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 11 12 13 14 15 16 17 18 19 20 21 22 23 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:37:05 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:37:04 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:37:02 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:37:01 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=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:37:01 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:36:58 Warning (5) MDD message timeout;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:36:57 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:36:45 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:36:35 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 11 12 13 14 15 16 17 18 19 20 21 22 23 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:36: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: 0 1.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:36:20 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1; 2020-05-14, 10:36: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=a0:04:60:fc:37:50;CMTS-MAC=00:01:5c:a2:6a:51;CM-QOS=1.1;CM-VER=3.1;
Thank you very much in advance for your support, ideas and feedback!
Model: CM1000|Ultra-High Speed Cable Modem—DOCSIS® 3.1 Ready
Message 1 of 1
Announcements
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more