NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear CM1000v2 | Periodic packet loss, errors within modem logs, reset complete and router swapped
Hey Everyone,
Appreciate the help in advance. We have been having issues with our internet the past 4 days and have been working to get to the source of the issue. This is our home network and the number of clients connected at one time rarely exceeds 5, 2 of which are hardwired in. We have gig speeds and the speed tests throughout these issues have been great, reading the gig speeds I would expect from our network.
Despite the speed tests, we have been getting random spikes in packet loss throughout the past 4 days, typically occurring once every 2ish minutes or less. The periodic packet loss will sometimes stop and we will get an hour, maybe two, of solid internet performance before the periodic packet loss begins again. After rebooting the modem, the performance is typically consistent for around 10-20 minutes before the packet loss begins occurring. Sometimes the reboot does not help at all and the packet loss begins as soon as the modem is back up. The loss is noticeable on all devices, wireless or wired. This only began the past 4 days, performance prior to this was excellent with absolutely 0 issues and no complaints.
I will provide the troubleshooting that has already been completed to clear out any initial troubleshooting methods and to provide further context into the issues.
- Router replaced (Originally thought to be the cause due to age of old router)
- Cabling from modem to router WAN port replaced
- Modem factory reset
- Modem hard rebooted (disconnected from power for 5 minutes then powered back on)
- Device hardwired directly to modem (issues still occur)
- Ensured no splitter or signal amplifier connected inside home
- Verified lights on modem (ON solid, DOWN solid, UP solid, INTERNET solid, LINK flashing)
- ISP remote modem reboot (JUST occurred as I was typing this out, impacted the results of the downstream bonded channels below as noted within the relevant section)
I will also paste the modem event log results and cabling information below. The top table, taken from the 'Downstream Bonded Channels' section used to show triple digit numbers in both the Correctable Codewords and Uncorrectable Codewords sections. We just had the ISP perform a remote reboot on the modem and following the reboot, the two codeword sections mentioned now shows all 0s. Could this have been what was impacting the performance and causing loss previously? Apologies for my lack of knowledge, I work in IT but my networking knowledge has always been pretty poor.
Appreciate any help anyone is able to provide.
| 1 | Locked | QAM256 | 1 | 507000000 Hz | -2.5 dBmV | 40.5 dB | 58698830 | 0 | 0 |
| 2 | Locked | QAM256 | 2 | 513000000 Hz | -2.4 dBmV | 40.8 dB | 58701871 | 0 | 0 |
| 3 | Locked | QAM256 | 3 | 519000000 Hz | -1.8 dBmV | 41.1 dB | 58705444 | 0 | 0 |
| 4 | Locked | QAM256 | 4 | 525000000 Hz | -1.4 dBmV | 41.2 dB | 58709294 | 0 | 0 |
| 5 | Locked | QAM256 | 5 | 531000000 Hz | -1.3 dBmV | 41.1 dB | 58713767 | 0 | 0 |
| 6 | Locked | QAM256 | 6 | 537000000 Hz | -1.3 dBmV | 41.1 dB | 58718209 | 0 | 0 |
| 7 | Locked | QAM256 | 7 | 543000000 Hz | -1.4 dBmV | 41.4 dB | 58722677 | 0 | 0 |
| 8 | Locked | QAM256 | 8 | 549000000 Hz | -1.7 dBmV | 41.3 dB | 58726192 | 0 | 0 |
| 9 | Locked | QAM256 | 9 | 555000000 Hz | -1.4 dBmV | 41.7 dB | 58730962 | 0 | 0 |
| 10 | Locked | QAM256 | 10 | 561000000 Hz | -1.1 dBmV | 41.6 dB | 58736006 | 0 | 0 |
| 11 | Locked | QAM256 | 11 | 567000000 Hz | -1.1 dBmV | 41.7 dB | 58774796 | 0 | 0 |
| 12 | Locked | QAM256 | 12 | 573000000 Hz | -1.3 dBmV | 41.7 dB | 58778192 | 0 | 0 |
| 13 | Locked | QAM256 | 13 | 579000000 Hz | -1.1 dBmV | 41.5 dB | 58782084 | 0 | 0 |
| 14 | Locked | QAM256 | 14 | 585000000 Hz | -0.9 dBmV | 41.8 dB | 58785376 | 0 | 0 |
| 15 | Locked | QAM256 | 15 | 591000000 Hz | -1.4 dBmV | 41.6 dB | 58789194 | 0 | 0 |
| 16 | Locked | QAM256 | 16 | 597000000 Hz | -1.5 dBmV | 41.5 dB | 58793337 | 0 | 0 |
| 17 | Locked | QAM256 | 17 | 603000000 Hz | -1.1 dBmV | 41.8 dB | 58797146 | 0 | 0 |
| 18 | Locked | QAM256 | 18 | 609000000 Hz | -1.4 dBmV | 41.7 dB | 58800738 | 0 | 0 |
| 19 | Locked | QAM256 | 19 | 615000000 Hz | -1.6 dBmV | 41.4 dB | 58803658 | 0 | 0 |
| 20 | Locked | QAM256 | 20 | 621000000 Hz | -1.6 dBmV | 41.3 dB | 58776781 | 0 | 0 |
| 21 | Locked | QAM256 | 21 | 627000000 Hz | -1.8 dBmV | 40.0 dB | 58818860 | 0 | 0 |
| 22 | Locked | QAM256 | 22 | 633000000 Hz | -1.8 dBmV | 40.5 dB | 58821794 | 0 | 0 |
| 23 | Locked | QAM256 | 23 | 639000000 Hz | -1.0 dBmV | 41.6 dB | 58825743 | 0 | 0 |
| 24 | Locked | QAM256 | 24 | 645000000 Hz | 0.2 dBmV | 42.4 dB | 58829423 | 0 | 0 |
| 25 | Locked | QAM256 | 25 | 651000000 Hz | 0.7 dBmV | 42.4 dB | 58832914 | 0 | 0 |
| 26 | Locked | QAM256 | 26 | 657000000 Hz | 0.8 dBmV | 42.6 dB | 58836924 | 0 | 0 |
| 27 | Locked | QAM256 | 27 | 663000000 Hz | 1.1 dBmV | 42.6 dB | 58840765 | 0 | 0 |
| 28 | Locked | QAM256 | 28 | 669000000 Hz | 0.9 dBmV | 42.5 dB | 58844769 | 0 | 0 |
| 29 | Locked | QAM256 | 29 | 675000000 Hz | 0.6 dBmV | 42.1 dB | 58847801 | 0 | 0 |
| 30 | Locked | QAM256 | 30 | 681000000 Hz | 0.5 dBmV | 42.6 dB | 58851738 | 0 | 0 |
| 31 | Locked | QAM256 | 31 | 687000000 Hz | 1.1 dBmV | 42.9 dB | 58854816 | 0 | 0 |
| 32 | Locked | QAM256 | 32 | 693000000 Hz | 0.9 dBmV | 42.8 dB | 58854912 | 0 | 0 |
| 1 | Locked | ATDMA | 1 | 19200000 Hz | 40.8 dBmV |
| 2 | Locked | ATDMA | 2 | 24000000 Hz | 43.5 dBmV |
| 3 | Locked | ATDMA | 3 | 30400000 Hz | 43.5 dBmV |
| 4 | Locked | ATDMA | 4 | 36800000 Hz | 44.0 dBmV |
| 5 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV |
| 6 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV |
| 7 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV |
| 8 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV |
| 2022-04-08, 17:09:44 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 17:04:57 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:58:12 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:56:50 | Notice (6) | US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 10 13.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:56:46 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:56:42 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:56:41 | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:55:53 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 2022-04-08, 16:55:16 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:50:26 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:48:05 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:41:57 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:39:19 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:35:55 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:31:06 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:29:57 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:23:56 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:19:17 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:17:13 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:15:45 | Critical (3) | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:15:28 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:13:56 | Critical (3) | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:13:33 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 16:11:58 | Critical (3) | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
| 2022-04-08, 15:58:50 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; |
3 Replies
Hey All,
After the ISP reset, all looked good and we had about 4 hours of consistent connection. Following the 4 hours of consistent internet, we then both received disconnection errors in the respective games we were playing and had around 30 seconds of extremely high packet loss. This is what was shown in the logs as soon as the issues began.
It's odd, the issues seem to always start with this line: Notice (6) - US profile assignment change. Once it goes through a few of these, it seems the T2, T3, and T4 errors begin to show up and we both become plagued with packet loss for 10-30 seconds. Any help would be greatly appreciated!
Time Priority Description 2022-04-08, 20:57:36 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:57:18 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:56:24 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:56:15 Notice (6) CM-STATUS message sent. Event Type Code: 6; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:56:14 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:55:44 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 10 13.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:55:25 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:55:22 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:54:31 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:54:00 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:53:56 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:52:21 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:51:52 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:50:01 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 10 13.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 20:47:54 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 10 13; New Profile: 11 13.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 17:57:04 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 17:09:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 17:04:57 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 16:58:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 16:56:50 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 10 13.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-08, 16:56:46 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; the ISP needs to check your line. The logs are indicating line issues and if you've done everything you can inside the home, then they're up to check external to the home. Reason it might work for a bit is a reset/reboot can have the modem connecting to different channels and those not have issues. But those channels change depending on the cmts and if it changes to ones that do have issues on them, then you'll see the problems.
Thanks so much for the help! These are the most recent results following a day of around 3 ping spikes resulting in temporary outages. I am guessing this supports more of what you mentioned with the ISP needing to visit the lines?
2022-04-09, 18:30:07 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 18:29:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 18:28:16 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 18:28:00 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 18:26:31 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 18:26:12 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 18:24:43 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 18:24:25 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 18:23:34 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 13:49:30 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 13:48:03 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 13:47:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 13:46:18 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 13:45:52 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 13:45:01 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 13:44:37 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; 2022-04-09, 13:43:10 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=9c:c9:eb:87:8b:28;CMTS-MAC=00:17:10:9d:3c:10;CM-QOS=1.1;CM-VER=3.1; Ch Lock Status Mod Channel ID Freq Power SNR Unerrored Correctable Uncorrectable
1 Locked QAM256 1 507000000 Hz -2.4 dBmV 40.3 dB 3496619053 1932 678
2 Locked QAM256 2 513000000 Hz -2.2 dBmV 40.7 dB 3496624797 1940 625
3 Locked QAM256 3 519000000 Hz -1.6 dBmV 41.0 dB 3496622841 1724 708
4 Locked QAM256 4 525000000 Hz -1.2 dBmV 41.2 dB 3496620086 1961 575
5 Locked QAM256 5 531000000 Hz -1.0 dBmV 41.2 dB 3496631593 2022 736
6 Locked QAM256 6 537000000 Hz -1.0 dBmV 41.3 dB 3496630116 2212 721
7 Locked QAM256 7 543000000 Hz -1.0 dBmV 41.3 dB 3496642382 1951 856
8 Locked QAM256 8 549000000 Hz -1.4 dBmV 41.2 dB 3496650800 1807 909
9 Locked QAM256 9 555000000 Hz -1.1 dBmV 41.5 dB 3496638133 1727 798
10 Locked QAM256 10 561000000 Hz -0.8 dBmV 41.6 dB 3496648831 1715 803
11 Locked QAM256 11 567000000 Hz -0.8 dBmV 41.5 dB 3498407996 1524 845
12 Locked QAM256 12 573000000 Hz -1.1 dBmV 41.6 dB 3498407437 1411 735
13 Locked QAM256 13 579000000 Hz -0.8 dBmV 41.6 dB 3498384206 1551 731
14 Locked QAM256 14 585000000 Hz -0.7 dBmV 41.8 dB 3498412196 1344 731
15 Locked QAM256 15 591000000 Hz -1.2 dBmV 41.5 dB 3498415329 1326 639
16 Locked QAM256 16 597000000 Hz -1.3 dBmV 41.3 dB 3498427697 1175 694
17 Locked QAM256 17 603000000 Hz -0.9 dBmV 41.6 dB 3498428068 1091 729
18 Locked QAM256 18 609000000 Hz -1.2 dBmV 41.5 dB 3498434066 1225 624
19 Locked QAM256 19 615000000 Hz -1.4 dBmV 41.5 dB 3498425686 1006 678
20 Locked QAM256 20 621000000 Hz -1.3 dBmV 41.0 dB 3498438376 972 739
21 Locked QAM256 21 627000000 Hz -1.5 dBmV 40.8 dB 3499219885 1105 696
22 Locked QAM256 22 633000000 Hz -1.5 dBmV 41.0 dB 3499230239 1062 682
23 Locked QAM256 23 639000000 Hz -0.7 dBmV 40.8 dB 3499232469 1127 635
24 Locked QAM256 24 645000000 Hz 0.5 dBmV 42.2 dB 3499229622 1039 931
25 Locked QAM256 25 651000000 Hz 0.9 dBmV 42.4 dB 3499237377 982 935
26 Locked QAM256 26 657000000 Hz 1.1 dBmV 42.5 dB 3499241955 953 752
27 Locked QAM256 27 663000000 Hz 1.4 dBmV 42.5 dB 3499248653 811 660
28 Locked QAM256 28 669000000 Hz 1.1 dBmV 42.5 dB 3499253046 730 631
29 Locked QAM256 29 675000000 Hz 0.7 dBmV 41.8 dB 3499246352 754 576
30 Locked QAM256 30 681000000 Hz 0.6 dBmV 42.5 dB 3499254099 734 540
31 Locked QAM256 31 687000000 Hz 1.2 dBmV 42.8 dB 3499624305 726 492
32 Locked QAM256 32 693000000 Hz 1.0 dBmV 42.7 dB 3499627124 784 492
