monks600
Tuning in
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Frequent daily dropouts and packet loss
Multiple engineers and still no fix in sight. One of the engineers did find a ‘nick’ in the coax half way down the ducting and repaired this. Seems to have stabilised the connection somewhat… few weeks after this, back to frequent packet loss and the latency had gone really poor again. This can be shown in the screen shots. The lower latency was just after the nick in the cable was fixed, still had packet loss though. And the other screen shot is from now. Ironically, no one is at the house as the moment and it’s just all over the show. Constant alerts from my firewall advising the main WAN connection has failed over to my 4G backup. If you look carefully at the top, you will see little red dots frequently which indicate communication loss to the modem.358Views0likes1CommentRe: Frequent daily dropouts and packet loss
Have another engineer booked for tomorrow morning so will see what the outcome is. 100% not my kit, left the hub in router mode with nothing attached via Ethernet and the issue is still apparent. I’ve even gone down the route of swapping physical cat5e drops as I pulled in spares and re terminating the ends and on the patch panel. Also glass ended both sides and still the same. i have two firewalls in a HA Pair and swapped the interfaces around and ran them in standalone mode, still the same. Fluke tested all my internal runs and they pass with little to no loss and are within the thresholds. curiousity got the better of me so I trace route out from my connection and went 3 hops down. Looks like there’s an issue with the edge cabinet (street cabinet) and the run back to the main hub. Doesn’t seem to be an issues from my property back to the edge cabinet. Running basics ping monitoring on each hop confirms this and the packet loss correlates with what I’m seeing. I have no experience with coax, as all the connections I deal with from isps on a daily basis are usually fiber, radio link or our own dark fiber. At this stage, networks team probably does need to get involved but I’m assuming this requires escalation from an on-site engineer. I’ve already requested on the past 2 visits to put me on a different feed in the cab as the main cable run seems to be fine from my property to the edge cabinet, this went on deaf ears though. we shall see what the outcome is. Pretty frustrating I’m nearly a month in and no one has a clue. Checked with neighbors but they’re all still on copper lines with open reach.442Views0likes0CommentsRe: Frequent daily dropouts and packet loss
Engineer attended on wednesday, replaced all internal cabeling and removed a booster out of the equation. Still the same outcome, 3.1 channel has lots of pre and post RS errors. The engineer advised this could be my kit possibly causing the interferance and advised to try router mode for a few days. I've done this, and it's made no difference what so ever. Don't understand how internal ethernet devices would cause pre and post RS errors on a single channel. But yeah, willing to try anything at this point. Here's a copy of the logs and how i currently stand: 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 36 2.5 3020730151 39220 Network Log Time Priority Description 20-05-2024 10:59:58 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; 20-05-2024 10:45:46 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; 20-05-2024 10:30:01 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; 20-05-2024 10:05: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; 20-05-2024 10:02:40 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; 20-05-2024 09:57:03 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; 20-05-2024 09:54:22 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; 20-05-2024 09:37:06 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; 20-05-2024 09:35:12 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; 20-05-2024 09:28:54 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; 20-05-2024 09:27: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 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 20-05-2024 09:23: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; 20-05-2024 09:22: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.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 20-05-2024 09:06: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; 20-05-2024 09:06:14 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; 20-05-2024 09:06: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; 20-05-2024 09:04: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 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 20-05-2024 08:45:45 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; 20-05-2024 08:44:43 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; 20-05-2024 08:42: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; 20-05-2024 08:40:08 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; 20-05-2024 08:39:39 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; 20-05-2024 08:39: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; 20-05-2024 08:37: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; 20-05-2024 08:36:00 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; 20-05-2024 08:32:43 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; 20-05-2024 08:25:23 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; 20-05-2024 08:21:35 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; 20-05-2024 08:20: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; 20-05-2024 08:16:57 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; 20-05-2024 08:13: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; 20-05-2024 08:06:43 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;446Views0likes0CommentsRe: Frequent daily dropouts and packet loss
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 0650Views0likes2CommentsRe: Frequent daily dropouts and packet loss
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 0712Views0likes0CommentsRe: Frequent daily dropouts and packet loss
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;838Views0likes2CommentsFrequent daily dropouts and packet loss
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 441451.4KViews0likes17Comments
