Hi all, I keep getting constant us profile assignment changes! I am posting my results below, can someone please advise if all is ok?
I see it too, always assumed it was just dithering over the link quality on a particular stream, if it's not giving performance problems, don't worry about it
Hi apologies am unable to cut and paste the results from router status,
| 1 | 322000000 | 2.8 | 41 | QAM 256 | 24 |
| 2 | 138000000 | 3.6 | 41 | QAM 256 | 1 |
| 3 | 146000000 | 3.2 | 41 | QAM 256 | 2 |
| 4 | 154000000 | 3 | 41 | QAM 256 | 3 |
| 5 | 162000000 | 3.1 | 41 | QAM 256 | 4 |
| 6 | 170000000 | 3.3 | 41 | QAM 256 | 5 |
| 7 | 178000000 | 3.5 | 41 | QAM 256 | 6 |
| 8 | 186000000 | 3.8 | 42 | QAM 256 | 7 |
| 9 | 194000000 | 4.1 | 42 | QAM 256 | 8 |
| 10 | 202000000 | 4.2 | 42 | QAM 256 | 9 |
| 11 | 218000000 | 4.4 | 42 | QAM 256 | 11 |
| 12 | 226000000 | 4.3 | 41 | QAM 256 | 12 |
| 13 | 234000000 | 4.1 | 41 | QAM 256 | 13 |
| 14 | 242000000 | 3.8 | 41 | QAM 256 | 14 |
| 15 | 250000000 | 3.5 | 41 | QAM 256 | 15 |
| 16 | 258000000 | 3.4 | 41 | QAM 256 | 16 |
| 17 | 266000000 | 3.3 | 42 | QAM 256 | 17 |
| 18 | 274000000 | 3.2 | 41 | QAM 256 | 18 |
| 19 | 282000000 | 3.4 | 41 | QAM 256 | 19 |
| 20 | 290000000 | 3.5 | 42 | QAM 256 | 20 |
| 21 | 298000000 | 3.3 | 41 | QAM 256 | 21 |
| 22 | 306000000 | 3.3 | 41 | QAM 256 | 22 |
| 23 | 314000000 | 2.9 | 41 | QAM 256 | 23 |
| 24 | 330000000 | 2.5 | 41 | QAM 256 | 25 |
| 25 | 338000000 | 2.6 | 41 | QAM 256 | 26 |
| 26 | 346000000 | 2.6 | 41 | QAM 256 | 27 |
| 27 | 354000000 | 2.4 | 41 | QAM 256 | 28 |
| 28 | 362000000 | 2.6 | 41 | QAM 256 | 29 |
| 29 | 370000000 | 2.5 | 41 | QAM 256 | 30 |
| 30 | 378000000 | 2.4 | 41 | QAM 256 | 31 |
| 31 | 386000000 | 2.5 | 41 | QAM 256 | 32 |
| 1 | Locked | 41 | 80 | 0 |
| 2 | Locked | 41 | 31 | 0 |
| 3 | Locked | 41 | 28 | 0 |
| 4 | Locked | 41 | 33 | 0 |
| 5 | Locked | 41 | 19 | 0 |
| 6 | Locked | 41 | 24 | 0 |
| 7 | Locked | 41 | 30 | 0 |
| 8 | Locked | 42 | 28 | 0 |
| 9 | Locked | 42 | 28 | 0 |
| 10 | Locked | 42 | 29 | 0 |
| 11 | Locked | 42 | 25 | 0 |
| 12 | Locked | 41 | 36 | 0 |
| 13 | Locked | 41 | 43 | 0 |
| 14 | Locked | 41 | 52 | 0 |
| 15 | Locked | 41 | 31 | 0 |
| 16 | Locked | 41 | 36 | 0 |
| 17 | Locked | 42 | 28 | 0 |
| 18 | Locked | 41 | 29 | 0 |
| 19 | Locked | 41 | 34 | 0 |
| 20 | Locked | 42 | 71 | 0 |
| 21 | Locked | 41 | 73 | 0 |
| 22 | Locked | 41 | 55 | 0 |
| 23 | Locked | 41 | 85 | 0 |
| 24 | Locked | 41 | 109 | 0 |
| 25 | Locked | 41 | 82 | 0 |
| 26 | Locked | 41 | 88 | 0 |
| 27 | Locked | 41 | 123 | 0 |
| 28 | Locked | 41 | 108 | 0 |
| 29 | Locked | 41 | 109 | 0 |
| 30 | Locked | 41 | 113 | 0 |
| 31 | Locked | 41 | 115 | 0 |
| 49600000 | 48.5 | 5120 | QAM 64 | 1 |
| 1 | 43100000 | 48.3 | 5120 | QAM 64 | 2 |
| 2 | 36600000 | 48.3 | 5120 | QAM 64 | 3 |
| 3 | 30100000 | 48.3 | 5120 | QAM 64 | 4 |
| 4 | 23600000 | 48 | 5120 | QAM 64 | 5 |
| 0 | ATDMA | 0 | 0 | 0 | 0 |
| 1 | ATDMA | 0 | 0 | 0 | 0 |
| 2 | ATDMA | 0 | 0 | 0 | 0 |
| 3 | ATDMA | 0 | 0 | 0 | 0 |
| 4 | ATDMA | 0 | 0 | 0 | 0 |
| 3-01-2026 23:27:07 | notice | US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 03-01-2026 20:15:42 | notice | US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 03-01-2026 18:54:46 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 03-01-2026 16:00:28 | notice | US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 03-01-2026 10:41:25 | notice | US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 03-01-2026 10:41:22 | notice | US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 03-01-2026 10:36:19 | notice | US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 01-01-2026 00:17:03 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
| 01-01-2026 00:16:53 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 01-01-2026 00:16:51 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 01-01-2026 00:16:49 | notice | Honoring MDD; IP provisioning mode = IPv4 |
| 01-01-2026 00:16:43 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 01-01-2026 00:16:43 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 22-12-2025 21:01:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 22-12-2025 21:01:22 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 22-12-2025 21:01:21 | critical | Cable Modem Reboot because of - tr069-reboot |
| 16-12-2025 00:58:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 16-12-2025 00:58:35 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 16-12-2025 00:58:34 | critical | Cable Modem Reboot because of - tr069-reboot |
| 08-12-2025 20:48:32 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
| 08-12-2025 20:48:32 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 12:00:59 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 12:00:59 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 12:00:52 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 12:00:25 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 12:00:25 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 12:00:19 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 11:59:44 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 11:59:44 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 11:59:39 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 11:59:39 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=8c:9a:8f:12:33:13;CMTS-MAC=00:01:5c:bf:9f:28;CM-QOS=1.1;CM-VER=3.1; |
| 04-12-2025 11:59:39 | critical | Started Unicast Maintenance Ranging - No Resp |
Forum TeamHi Gparky👋
We’re sorry to hear you’re having issues with your router. We’re here to help! To assist you, we’ll need to access your account, which requires completing security questions.
We’ll send you a private message shortly—please keep an eye out for it.
Hello I have not received any
message
Is anyone going to help?
I see it too, always assumed it was just dithering over the link quality on a particular stream, if it's not giving performance problems, don't worry about it
Thank you, but are my specs in range? Or is something wrong?
SNR good, levels a smidge high but well within target, +/- 3 is excellent, +/-6 ok, if you happen to have been left with a spare 3dB attenuator, add it onto the hub, but that's really only to spit and polish the levels to perfection, mine were a touch high but not causing any problem, and I did have an attenuator, probably left over from the days of STB only and no splitter, but they don't need sweating over unless things are going badly.
PS. Mine flaps similarly on ID 10, the 210000000Hz frequency for me, yours flaps on ID 12, 226000000Hz - wonder if there may be some interference creeping in on those frequencies causing it to reassess the parameters
Sorry so is my results good?
