Forum Discussion

chr120's avatar
chr120
Joining in
2 years ago

Constant Disconnects - US profile assignment change

As the title suggests over the last few days I've been plagued by constant disconnects that last a long while. I'm tethering off my mobile phone to post this as my broadband won't load any pages - effectively the connection is unusable in its current state. I've tried reaching out to support directly over the phone but they're closed.

Network Log

13-01-2024 20:01:12 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 19:35:29 notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 17:11:40 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 16:24:00 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 15:20:11 notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 13:12:34 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 12:08:45 notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 09:59:27 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 01:30:38 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 00:49:19 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 00:34:56 notice REGISTRATION COMPLETE - Waiting for Operational status
13-01-2024 00:34:49 critical No Ranging Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 00:34:44 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 00:34:36 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 00:34:34 notice Honoring MDD; IP provisioning mode = IPv4
13-01-2024 00:34:12 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<REDACT>;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-01-2024 00:34:11 critical Cable Modem Reboot because of - HW or Power-On Reset
05-01-2024 14:01:55 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
05-01-2024 14:01:20 critical No Ranging Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
05-01-2024 14:01:01 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
05-01-2024 14:00:54 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
05-01-2024 14:00:52 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
04-01-2024 20:23:14 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
29-12-2023 15:11:47 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
27-12-2023 12:17:29 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
26-12-2023 06:42:19 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
25-12-2023 04:36:26 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
24-12-2023 23:37:18 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
24-12-2023 01:28:45 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
23-12-2023 00:03:02 critical No Ranging Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
23-12-2023 00:02:40 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
23-12-2023 00:02:39 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;

Downstream Log

 

3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 331000000 11.6 39 QAM 256 25
2 139000000 11.6 38 QAM 256 1
3 147000000 11.2 38 QAM 256 2
4 155000000 10.9 37 QAM 256 3
5 163000000 10.6 37 QAM 256 4
6 171000000 10.6 38 QAM 256 5
7 179000000 10.7 38 QAM 256 6
8 187000000 10.8 38 QAM 256 7
9 195000000 10.8 38 QAM 256 8
10 203000000 10.2 38 QAM 256 9
11 211000000 9.4 38 QAM 256 10
12 219000000 8.5 38 QAM 256 11
13 227000000 8.5 38 QAM 256 12
14 235000000 8.8 38 QAM 256 13
15 243000000 8.5 38 QAM 256 14
16 251000000 8.3 38 QAM 256 15
17 259000000 9.2 38 QAM 256 16
18 267000000 9.9 38 QAM 256 17
19 275000000 10.5 39 QAM 256 18
20 283000000 11.2 39 QAM 256 19
21 291000000 11.4 39 QAM 256 20
22 299000000 11.5 39 QAM 256 21
23 307000000 11.5 39 QAM 256 22
24 315000000 11.3 39 QAM 256 23
25 323000000 11.4 39 QAM 256 24
26 339000000 12.3 38 QAM 256 26
27 347000000 12.3 39 QAM 256 27
28 355000000 11.3 39 QAM 256 28
29 363000000 10.6 39 QAM 256 29
30 371000000 10.1 39 QAM 256 30
31 379000000 9.4 39 QAM 256 31

3.0 Downstream channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 39 15 0
2 Locked 38 137 0
3 Locked 38 126 0
4 Locked 37 121 0
5 Locked 37 128 0
6 Locked 38 114 0
7 Locked 38 89 0
8 Locked 38 85 0
9 Locked 38 83 0
10 Locked 38 59 0
11 Locked 38 64 0
12 Locked 38 59 0
13 Locked 38 62 0
14 Locked 38 50 0
15 Locked 38 56 0
16 Locked 38 35 0
17 Locked 38 19 0
18 Locked 38 23 0
19 Locked 39 17 0
20 Locked 39 6 0
21 Locked 39 13 0
22 Locked 39 11 0
23 Locked 39 17 0
24 Locked 39 12 0
25 Locked 39 13 0
26 Locked 38 7 0
27 Locked 39 13 0
28 Locked 39 15 0
29 Locked 39 14 0
30 Locked 39 14 0
31 Locked 39 25 0

3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
39 94 4K 1840 QAM 4096 1108

3.1 Downstream channels
Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
39 Locked 42 11.8 1132116532 3

Upstream Log

3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 49600000 41 5120 QAM 16 5
1 43100000 40.8 5120 QAM 16 6
2 36600000 40.8 5120 QAM 16 7
3 30100000 40.8 5120 QAM 16 8
4 23600000 41.5 5120 QAM 16 11

3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0 ATDMA 0 0 1 0
1 ATDMA 0 0 2 0
2 ATDMA 0 0 5 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 2 0

3.1 Upstream channels
Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
12 11 36.5 2K QAM 256

3.1 Upstream channels
Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
12 OFDMA 220 74000000 0 0

Configuration

Network access Allowed
Maximum Number of CPEs 1
Baseline Privacy Enabled
DOCSIS Mode 3.1
Config file cmreg-vmdg660-bbt076-b.cm

Primary Downstream Service Flow
SFID 27800
Max Traffic Rate 1230000450 bps
Max Traffic Burst 42600bytes
Min Traffic Rate 0 bps

Primary Upstream Service Flow
SFID 27799
Max Traffic Rate 110000274 bps
Max Traffic Burst 42600bytes
Min Traffic Rate 0 bps
Max Concatenated Burst 42600bytes
Scheduling Type Best Effort

Status

Cable Modem Status
Item Status Type
Cable Modem Status Online DOCSIS 3.0
Primary downstream channel Locked SC-QAM
Channel Overview Downstream Upstream
DOCSIS 3.0 channels 31 5
DOCSIS 3.1 channels 1 1

  • John_GS's avatar
    John_GS
    Forum Team
    2 years ago

    Hi chr120 

    Thanks for posting and welcome to the community.

    Very sorry for any broadband issues.

    I've checked and you are affected by an SNR issue - Signal to Noise ratio. 

    F011153188 - this is the fault number. The estimated fix date is today at 1.15pm.

    • chr120's avatar
      chr120
      Joining in
      2 years ago

      Hi John_GS

      Thank you for responding. Unfortunately today has been particularly bad again, plagued with constant disconnects and just what feels like poor quality connection even when connected (takes forever to load webpages etc). I've once again had to use my phone to tether for work etc. Is there any other / more information I could provide that might help get a resolution here? Please let me know.

      Network Log

      17-01-2024 12:12:44 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 11:57:27 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 08:37:21 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 08:35:49 notice CM-STATUS message sent. Event Type Code: 23; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 08:35:45 notice CM-STATUS message sent. Event Type Code: 20; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 08:35:45 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 08:13:50 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 06:41:36 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:22:36 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      17-01-2024 05:22:33 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:22:24 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:21:30 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      17-01-2024 05:21:27 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:21:14 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:17:46 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:17:23 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      17-01-2024 05:17:20 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:15:43 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 8 9 10 13 14 15 16 17 18 19 20 21 22 23 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:15:31 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      17-01-2024 05:15:24 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:14:30 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 9 10 13 14 15 16 17 18 19 20 21 22 23 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:14:25 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      17-01-2024 05:14:16 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:13:33 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 9 10 13 14 15 16 17 18 19 20 21 22 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:13:32 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      17-01-2024 05:13:04 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:12:21 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 10 13 15 16 18 19 21 22 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:12:09 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      17-01-2024 05:11:54 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:11:41 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      17-01-2024 05:11:40 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 6 7 10 13 15 16 21 22 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 05:11:20 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;

    • chr120's avatar
      chr120
      Joining in
      2 years ago

      Hi @John_GS

      Same issues today, can't hold meetings, can't properly browse the internet without up & downs. Anything more I can do from my side to get the service back to normal?

      Network Log

      18-01-2024 11:32:39 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 11:12:40 notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 11:00:28 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 10:55:30 notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 10:24:11 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 09:45:35 notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 08:32:06 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 08:29:11 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 06:50:22 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 06:39:55 notice CM-STATUS message sent. Event Type Code: 23; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 06:20:44 notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 05:41:29 notice CM-STATUS message sent. Event Type Code: 23; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 05:33:13 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 05:00:26 notice US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 04:48:23 notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 04:46:15 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 04:25:15 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 04:25:08 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM
      18-01-2024 04:24:55 warning MDD message timeout;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 04:17:45 notice CM-STATUS message sent. Event Type Code: 23; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 04:17:34 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 04:17:34 notice CM-STATUS message sent. Event Type Code: 20; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 03:33:22 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 03:27:36 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 02:36:50 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 01:37:22 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 01:00:52 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 00:53:54 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 00:53:36 notice CM-STATUS message sent. Event Type Code: 22; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      18-01-2024 00:35:03 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 23:17:11 notice CM-STATUS message sent. Event Type Code: 23; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;
      17-01-2024 12:12:44 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REDACT>;CMTS-MAC=<REDACT>;CM-QOS=1.1;CM-VER=3.1;

       

      • John_GS's avatar
        John_GS
        Forum Team
        12 months ago

        Hi chr120 

         

        Thanks for coming back to me. Just letting you know I've checked the ticket and the fix has gone in, final testing is currently being done.

        Best wishes.