Frequent daily dropouts and packet loss

[monks600]

Hi,

Was wonderinfg if someone on the forum mods team could help?

I'm experiencing frequent packet loss and drop outs on a daily basis. Note, my router is sat in modem mode and i'm monitoring both the gateway and an external service. Upon looking at the logs i can see a lot of post errors on the 3.1 channel but all other channels are pretty much perfect, just seems to be an issue with the 3.1 channel.

Rebooting the modem does nothing, same scenario thorughout the day. Luckily i have a 4G backup, so it's not much of an issue but i'd like this looking at please.

- All Coax connections have been re-seated internally and external of the property and are tight. No visible damge either

- Modem has been rebooted multiple times

See below:

3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 330000000 4.7 40 QAM 256 25
2 202000000 4.2 40 QAM 256 9
3 210000000 4.7 40 QAM 256 10
4 218000000 5 40 QAM 256 11
5 226000000 5 40 QAM 256 12
6 234000000 4.9 40 QAM 256 13
7 242000000 4.7 40 QAM 256 14
8 250000000 4.7 40 QAM 256 15
9 258000000 4.6 40 QAM 256 16
10 266000000 4.8 40 QAM 256 17
11 274000000 4.9 40 QAM 256 18
12 282000000 5.2 40 QAM 256 19
13 290000000 5.2 40 QAM 256 20
14 298000000 5.3 40 QAM 256 21
15 306000000 5.2 40 QAM 256 22
16 314000000 5 40 QAM 256 23
17 322000000 5 40 QAM 256 24
18 338000000 5.2 40 QAM 256 26
19 346000000 5.1 40 QAM 256 27
20 354000000 5.3 40 QAM 256 28
21 362000000 5.3 40 QAM 256 29
22 370000000 5.1 40 QAM 256 30
23 378000000 5 40 QAM 256 31
24 386000000 4.5 39 QAM 256 32
25 394000000 4.6 41 QAM 256 33
26 402000000 4.2 41 QAM 256 34
27 410000000 4.5 41 QAM 256 35
28 418000000 4.3 41 QAM 256 36
29 426000000 4.6 40 QAM 256 37
30 434000000 4.6 41 QAM 256 38
31 442000000 4.6 41 QAM 256 39
32 450000000 5 41 QAM 256 40

3.0 Downstream channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40 0 0
2 Locked 40 7 0
3 Locked 40 13 0
4 Locked 40 11 0
5 Locked 40 5 0
6 Locked 40 1 0
7 Locked 40 0 0
8 Locked 40 0 0
9 Locked 40 0 0
10 Locked 40 0 0
11 Locked 40 0 0
12 Locked 40 0 0
13 Locked 40 0 0
14 Locked 40 0 0
15 Locked 40 0 0
16 Locked 40 0 0
17 Locked 40 0 0
18 Locked 40 1 0
19 Locked 40 0 0
20 Locked 40 0 0
21 Locked 40 0 0
22 Locked 40 0 0
23 Locked 40 0 0
24 Locked 39 0 0
25 Locked 41 0 0
26 Locked 41 1 0
27 Locked 41 0 0
28 Locked 41 0 0
29 Locked 40 0 0
30 Locked 41 0 0
31 Locked 41 0 0
32 Locked 41 0 0

3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159 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)
159 Locked 37 2.6 2456731718 44199

Router status

Status
Downstream
Upstream
Configuration
Network Log

Refresh data

Network Log
Time Priority Description
01-05-2024 10:33:02 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 10:28:56 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 10:28:49 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 10:24:02 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 10:14:56 notice GUI Login Status - Login Success from LAN interface
01-05-2024 10:08:20 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 10:03:56 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:59:55 notice GUI Login Status - Login Success from LAN interface
01-05-2024 09:59:33 notice GUI Login Status - Login Fail from LAN interface
01-05-2024 09:42:24 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:39:19 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:37:36 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:36:38 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:20:25 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:19:21 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:19:06 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:14:37 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:07:13 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 09:03:57 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 08:54:34 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 08:54:34 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 08:36:39 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 08:34:23 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 08:31:21 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 08:24:59 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 08:20:37 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 07:45:08 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 07:45:08 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 07:23:53 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 07:23:53 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 07:03:42 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 07:00:11 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 06:51:10 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 06:48:47 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 06:46:34 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Log out Language

Home
Modem mode
Advanced settings
Tools
Network status
LED light
Admin

Cable Modem Status

Status
Downstream
Upstream
Configuration
Network Log

Refresh data

3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 330000000 4.9 40 QAM 256 25
2 202000000 4.4 40 QAM 256 9
3 210000000 4.9 40 QAM 256 10
4 218000000 5.2 40 QAM 256 11
5 226000000 5.2 40 QAM 256 12
6 234000000 5.1 40 QAM 256 13
7 242000000 4.9 40 QAM 256 14
8 250000000 4.8 40 QAM 256 15
9 258000000 4.8 40 QAM 256 16
10 266000000 5 40 QAM 256 17
11 274000000 5 40 QAM 256 18
12 282000000 5.3 40 QAM 256 19
13 290000000 5.4 40 QAM 256 20
14 298000000 5.5 40 QAM 256 21
15 306000000 5.4 40 QAM 256 22
16 314000000 5.2 40 QAM 256 23
17 322000000 5.3 40 QAM 256 24
18 338000000 5.5 40 QAM 256 26
19 346000000 5.4 40 QAM 256 27
20 354000000 5.4 40 QAM 256 28
21 362000000 5.5 40 QAM 256 29
22 370000000 5.3 40 QAM 256 30
23 378000000 5.4 40 QAM 256 31
24 386000000 4.8 40 QAM 256 32
25 394000000 4.8 41 QAM 256 33
26 402000000 4.4 41 QAM 256 34
27 410000000 4.7 41 QAM 256 35
28 418000000 4.6 41 QAM 256 36
29 426000000 4.8 41 QAM 256 37
30 434000000 4.8 41 QAM 256 38
31 442000000 4.8 41 QAM 256 39
32 450000000 5.3 41 QAM 256 40

3.0 Downstream channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40 0 0
2 Locked 40 7 0
3 Locked 40 13 0
4 Locked 40 11 0
5 Locked 40 5 0
6 Locked 40 1 0
7 Locked 40 0 0
8 Locked 40 0 0
9 Locked 40 0 0
10 Locked 40 0 0
11 Locked 40 0 0
12 Locked 40 0 0
13 Locked 40 0 0
14 Locked 40 0 0
15 Locked 40 0 0
16 Locked 40 0 0
17 Locked 40 0 0
18 Locked 40 1 0
19 Locked 40 0 0
20 Locked 40 0 0
21 Locked 40 0 0
22 Locked 40 0 0
23 Locked 40 0 0
24 Locked 40 0 0
25 Locked 41 0 0
26 Locked 41 1 0
27 Locked 41 0 0
28 Locked 41 0 0
29 Locked 41 0 0
30 Locked 41 0 0
31 Locked 41 0 0
32 Locked 41 0 0

3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159 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)
159 Locked 37 2.9 2446644265 44145

[Sephiroth]

I know you asked for help from the Forum Team - and in a couple of days you’ll get your turn.

Frustratingly, they may ask you to put your hub into router mode so that they can do all of their tests.  This will waste your time as the problem lies 100% on the DOCSIS 3.1 side - their network.  The error codes 16 & 24 in the network log report that the FEC error limits have been broken and recovery has been instituted.  This is what the Forum Team need to deal with and nothing else.

From your side, it would help if you can monitor this, looking for the events in the Network Log and seriously rising Uncorrectable Errors and reporting back via ths thread.

If you’re really “lucky”, the Forum Team will accept the downstream problem and offer you a tech visit which will achieve nothing other than the possibility of the tech raising the problem with Networks.  If you’re really lucky, the Forum Team will raise this with network bit evidence of continuous issues should be posted for that to happen.

Do keep us posted.   

[monks600]

Thanks for the reply. Appreciate the time and effort.

just looked again, 3.1 channel is constantly rising with pre and post errors. All other channels absolutely fine and zero. Been like this for a few weeks, didn't really notice it because the primary WAN was failing over in the background to the 4G connection and my alerting stopped working from telegram. 

3.1 Downstream channels
Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV)

Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
159 Locked 36 2.8 2565890714              47437

More in the network referring to error codes 16 & 24

Network Log
Time Priority Description
01-05-2024 13:36:51 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 13:36:51 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 13:34:28 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 13:28:24 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 13:23:06 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 13:11:26 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 13:11:08 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:58:52 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:54:00 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:50:53 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:49:29 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:41:16 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:35:32 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:32:27 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:28:00 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:28:00 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:26:14 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:26:14 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:24:09 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:17:38 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:16:37 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:16:10 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:16:10 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:15:38 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:14:28 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:12:32 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:12:12 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:10:18 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:09:55 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:06:45 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:06:42 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-05-2024 12:04:43 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Sephiroth]

Yes - your downstream is failing.   The D3.1 channel is the workhorse.  Corrected errors are quite normal given the very high speed, encoding and modulation.  The uncorrected errors, as you know, are lost data.  This will need a tech in the first instance who can try a replacement hub.

[Robert_P]

Hello monks600

Sorry to hear of the connection issues experienced, we appreciate you raising this via the forums.

I will send you a Private Message to get some more details from you to assist. Check the envelope in the top right of the forum when signed in for the message.

Rob

[monks600]

Hi there,

Engineer attended, advised nothing wrong with the power levels and nothing being shown on the tester faults wise. Advised the 3.1 channel is really bad and showed him the status page and he's advsed there's not much he can do apart from swap out the Modem/Router.

Modem/Router has since been swapped, the issue still persists, if not worse than before. I'm still seeing really frequent/high post RS on the 3.1 channel. Everything else is absolutely fine on the other channels, no pre or post errors at all. 

Seems everything is pointing towards the 3.1 channel again. Below is with the new router (installed yesterday):

Note: Modem was rebooted 5 mins prior to the below:

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)

159

Locked

37

2.2

64052307

47

and as you can see, all other bondend channels are fine:

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	330000000	4.4	40	QAM 256	25
2	138000000	4.5	40	QAM 256	1
3	146000000	4.3	40	QAM 256	2
4	154000000	4.1	40	QAM 256	3
5	162000000	3.9	40	QAM 256	4
6	170000000	3.7	40	QAM 256	5
7	194000000	3.7	40	QAM 256	8
8	202000000	3.9	40	QAM 256	9
9	226000000	4.7	40	QAM 256	12
10	234000000	4.6	40	QAM 256	13
11	258000000	4.3	40	QAM 256	16
12	266000000	4.4	40	QAM 256	17
13	274000000	4.4	40	QAM 256	18
14	282000000	4.7	40	QAM 256	19
15	290000000	4.7	40	QAM 256	20
16	298000000	4.9	40	QAM 256	21
17	306000000	4.7	40	QAM 256	22
18	314000000	4.6	40	QAM 256	23
19	322000000	4.6	40	QAM 256	24
20	338000000	4.8	40	QAM 256	26
21	346000000	4.7	40	QAM 256	27
22	354000000	4.9	40	QAM 256	28
23	362000000	4.9	40	QAM 256	29
24	370000000	4.8	40	QAM 256	30
25	378000000	4.8	40	QAM 256	31
26	386000000	4.2	40	QAM 256	32
27	394000000	4.2	41	QAM 256	33
28	402000000	3.8	40	QAM 256	34
29	410000000	4.1	41	QAM 256	35
30	418000000	4	40	QAM 256	36
31	426000000	4.2	41	QAM 256	37
32	442000000	4.2	41	QAM 256	39

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	40	0	0
2	Locked	40	0	0
3	Locked	40	0	0
4	Locked	40	0	0
5	Locked	40	0	0
6	Locked	40	0	0
7	Locked	40	0	0
8	Locked	40	0	0
9	Locked	40	0	0
10	Locked	40	0	0
11	Locked	40	0	0
12	Locked	40	0	0
13	Locked	40	0	0
14	Locked	40	0	0
15	Locked	40	0	0
16	Locked	40	0	0
17	Locked	40	0	0
18	Locked	40	0	0
19	Locked	40	0	0
20	Locked	40	0	0
21	Locked	40	0	0
22	Locked	40	0	0
23	Locked	40	0	0
24	Locked	40	0	0
25	Locked	40	0	0
26	Locked	40	0	0
27	Locked	41	0	0
28	Locked	40	0	0
29	Locked	41	0	0
30	Locked	40	0	0
31	Locked	41	0	0
32	Locked	41	0	0

[monks600]

Latency is constntly high with little to no load on the network. 

[monks600]

Anyone able to advise on the next steps? I can only now assume it's the hardward upstream that's having issues.

[Sephiroth]

What high post-RS errors on the D3.1 channel?  The BQM is at odds with what you posted.  When the yellow spikes are high, it's usually a downstream problem (blue would indicate upstream).  So a refresh on the D3.1 figures and an indication of the uptime would be helpful.

[monks600]

Downstream on 3.1 as per the below:

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)

159

Locked

36

1.5

2577164742

47452

And 3.0 channels:

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	40	0	0
2	Locked	40	0	0
3	Locked	40	0	0
4	Locked	40	0	0
5	Locked	40	0	0
6	Locked	40	0	0
7	Locked	40	0	0
8	Locked	40	0	0
9	Locked	40	0	0
10	Locked	40	0	0
11	Locked	40	0	0
12	Locked	40	0	0
13	Locked	40	0	0
14	Locked	40	0	0
15	Locked	40	0	0
16	Locked	40	0	0
17	Locked	40	0	0
18	Locked	40	0	0
19	Locked	40	0	0
20	Locked	40	0	0
21	Locked	40	0	0
22	Locked	40	0	0
23	Locked	40	0	0
24	Locked	40	0	0
25	Locked	40	0	0
26	Locked	40	0	0
27	Locked	41	0	0
28	Locked	41	0	0
29	Locked	41	0	0
30	Locked	41	0	0
31	Locked	41	0	0
32	Locked	41	0	0