3 weeks ago
I’ve been getting my internet through cable for more the 27 years originally with Telecential, via all the intermediate providers to Virgin Media. Once originally set up, it has mostly been reliable except for a few area outages from time to time. Unfortunately, since 27-Feb, the connexion has been significantly degraded with intermittent high packet loss culminating in effective disconnexion from the internet for periods of approximately 5 minutes at a time. These disconnexions happen several times a day seemingly at random. I’m currently on a 1Gb contract with copper to the house (not least due to age of connexion) and have a Hub 5. The hub was updated and put in place Nov-2023 and worked perfectly until 27-Feb.
I’ve contacted VM support numerous times without significant success. I run the CM in Modem Mode. It was only at the penultimate support call that the VM representative informed me that they cannot really support CMs running in Modem Mode. I wish they said that on the first call. It would have saved a lot of elapse time.
So, I spent time this week reorganising my house network so that I could run the CM in regular Router Mode. Due to limitations of the Hub 5 only supporting the 192.168.0.0/24 subnets on the pirate network side, this involved changing to a different private IP address space - not a particularly simple task. It’s done now, so I can finally run the CM in Router Mode and get some more support. I’ve been running the CM in Router Mode for the last few of days with a single laptop connected to the 192.168.0.0/24 subnet and the rest of my house network connected to its usual router configured as the CM’s DMZ. Both the laptop and the rest of the house network seem to work in this setup when the cable connexion is working.
To help troubleshoot the problem, I’ve set up a session on the laptop and in the house network pinging one of VM’s DNS server (194.168.4.100) every 10 seconds. This alerts me when things start to get flakey. I’ve also set up a ThinkBroadband Monitor to keep an eye out the connexion from the other side.
There have been several outages today including one just around lunchtime. Just after this occurred, I phoned up VM support and eventually got through to a a rep who did some test and said that its all working ok. Of course, by the time I’d got through to support and he’d started his test, It had indeed started working again. That’s the nature of intermittent faults. He said he could do nothing to help and that I should phone back when it happens again.
Does anybody know how to get this type of intermittent problems resolved?
Any help would be greatly appreciated. Thanks.
Here is a snapshot of today’s ThinkBroadband monitor:
Network long looks like this
Network Log
Time | Priority | Description |
12-04-2024 18:16:30 | notice | GUI Login Status - Login Success from LAN interface |
12-04-2024 18:07:59 | notice | CM-STATUS message sent. Event Type Code: 16; 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; |
12-04-2024 18:06:29 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 18:01:11 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:53:10 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:52:47 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:52:46 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:48:07 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:47:44 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:46:45 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:46:42 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:46:04 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:45:38 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:44:36 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:44:20 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:44:03 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:43:23 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:42:58 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:42:57 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:42:36 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:42:22 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:42:14 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:42:04 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:42:00 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:41:59 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:41:44 | notice | GUI Login Status - Login Success from LAN interface |
12-04-2024 17:41:38 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:41:30 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:41:27 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:41:12 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:40:41 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:40:06 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:39:54 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-04-2024 17:39:51 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
3 weeks ago
Looks like you are maxing out your upload a fair bit causing high latency but the main issue is that your downstream is broken. Needs a technician visit and if he can't find anything wrong between last cabinet and your home a network engineer.
3 weeks ago
Can you post up the rest of the Hub data. as per this.
Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts
3 weeks ago
@IPFreely wrote:Looks like you are maxing out your upload a fair bit causing high latency
latency would be higher then that on VM rate limiting
2 weeks ago
So, something clearly happened Friday night as the occurrence of unavailability went down significantly, and the BQM graphs changed. This morning, I am getting almost no disconnects but regular low level packet loss when the connexion is in use. Is this level of packet loss to be expected? I'd not think so. It causes occasional slowness.
2024-04-13 graph
2024-04-14 graph
2024-04-15 graph
2 weeks ago
Here are the Downstream tables
3.0 Downstream channels
1 | 611000000 | 4.3 | 42 | QAM 256 | 26 |
2 | 411000000 | 4.6 | 43 | QAM 256 | 1 |
3 | 419000000 | 5.4 | 43 | QAM 256 | 2 |
4 | 427000000 | 4.7 | 43 | QAM 256 | 3 |
5 | 435000000 | 2.9 | 42 | QAM 256 | 4 |
6 | 443000000 | 1.1 | 42 | QAM 256 | 5 |
7 | 451000000 | -2 | 40 | QAM 256 | 6 |
8 | 459000000 | 0.5 | 41 | QAM 256 | 7 |
9 | 467000000 | 2.6 | 42 | QAM 256 | 8 |
10 | 475000000 | 3.7 | 43 | QAM 256 | 9 |
11 | 483000000 | 2.5 | 42 | QAM 256 | 10 |
12 | 491000000 | 0.2 | 41 | QAM 256 | 11 |
13 | 499000000 | -3.2 | 39 | QAM 256 | 12 |
14 | 507000000 | -2.7 | 40 | QAM 256 | 13 |
15 | 515000000 | 1.2 | 42 | QAM 256 | 14 |
16 | 523000000 | 3.1 | 42 | QAM 256 | 15 |
17 | 531000000 | 1.4 | 42 | QAM 256 | 16 |
18 | 539000000 | 0.3 | 41 | QAM 256 | 17 |
19 | 547000000 | -2.9 | 40 | QAM 256 | 18 |
20 | 555000000 | -1 | 41 | QAM 256 | 19 |
21 | 563000000 | 1.4 | 42 | QAM 256 | 20 |
22 | 571000000 | 4.1 | 43 | QAM 256 | 21 |
23 | 579000000 | 3.8 | 42 | QAM 256 | 22 |
24 | 587000000 | 1.4 | 41 | QAM 256 | 23 |
25 | 595000000 | 1.1 | 41 | QAM 256 | 24 |
26 | 603000000 | 2.4 | 42 | QAM 256 | 25 |
27 | 619000000 | 4.9 | 42 | QAM 256 | 27 |
28 | 627000000 | 5.2 | 42 | QAM 256 | 28 |
29 | 635000000 | 4.6 | 42 | QAM 256 | 29 |
30 | 643000000 | 4.4 | 42 | QAM 256 | 30 |
31 | 651000000 | 4.3 | 42 | QAM 256 | 31 |
32 | 659000000 | 3.5 | 42 | QAM 256 | 32 |
3.0 Downstream channels
1 | Locked | 42 | 9 | 0 |
2 | Locked | 43 | 2 | 0 |
3 | Locked | 43 | 3 | 0 |
4 | Locked | 43 | 1 | 0 |
5 | Locked | 42 | 6 | 0 |
6 | Locked | 42 | 6 | 0 |
7 | Locked | 40 | 109 | 0 |
8 | Locked | 41 | 34 | 0 |
9 | Locked | 42 | 5 | 0 |
10 | Locked | 43 | 3 | 0 |
11 | Locked | 42 | 1 | 0 |
12 | Locked | 41 | 19 | 0 |
13 | Locked | 39 | 452 | 0 |
14 | Locked | 40 | 279 | 0 |
15 | Locked | 42 | 6 | 0 |
16 | Locked | 42 | 5 | 0 |
17 | Locked | 42 | 8 | 0 |
18 | Locked | 41 | 38 | 0 |
19 | Locked | 40 | 347 | 0 |
20 | Locked | 41 | 102 | 0 |
21 | Locked | 42 | 11 | 0 |
22 | Locked | 43 | 4 | 0 |
23 | Locked | 42 | 10 | 0 |
24 | Locked | 41 | 12 | 0 |
25 | Locked | 41 | 29 | 0 |
26 | Locked | 42 | 12 | 0 |
27 | Locked | 42 | 10 | 0 |
28 | Locked | 42 | 12 | 0 |
29 | Locked | 42 | 11 | 0 |
30 | Locked | 42 | 17 | 0 |
31 | Locked | 42 | 11 | 0 |
32 | Locked | 42 | 13 | 0 |
3.1 Downstream channels
159 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
159 | Locked | 39 | -7.0 | 333386508 | 3849181 |
2 weeks ago
Here are the Upstream tables
3.0 Upstream channels
0 | 49600000 | 45.3 | 5120 | QAM 64 | 9 |
1 | 43100000 | 44.3 | 5120 | QAM 64 | 10 |
2 | 36600000 | 43.5 | 5120 | QAM 64 | 11 |
3 | 30100000 | 43.5 | 5120 | QAM 64 | 12 |
4 | 23600000 | 43 | 5120 | QAM 64 | 13 |
3.0 Upstream channels
0 | ATDMA | 0 | 0 | 4 | 0 |
1 | ATDMA | 0 | 0 | 2 | 1 |
2 | ATDMA | 0 | 0 | 0 | 1 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
3.1 Upstream channels
14 | 10 | 39.0 | 2K | QAM 256 |
3.1 Upstream channels
14 | OFDMA | 200 | 74000000 | 2 | 0 |
2 weeks ago
Network log from today just some packet loss
Network Log
15-04-2024 10:33:18 | 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; |
15-04-2024 10:21:35 | notice | GUI Login Status - Login Success from LAN interface |
15-04-2024 09:00:48 | notice | GUI Login Status - Login Success from LAN interface |
15-04-2024 08:57:42 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
15-04-2024 08:55:36 | 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; |
15-04-2024 08:55:35 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 10 11 12 13 14 15 18 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
15-04-2024 08:55:33 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
15-04-2024 08:25:47 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 10 11 12 13 14 15 18 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
15-04-2024 08:25:35 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
15-04-2024 07:58:41 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
15-04-2024 07:56:35 | 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; |
15-04-2024 06:38:57 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
15-04-2024 01:38:12 | 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; |
15-04-2024 01:38:12 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
15-04-2024 00:36:27 | 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; |
15-04-2024 00:36:27 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 21:56:47 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 21:54:40 | 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; |
14-04-2024 21:51:28 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 21:49: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; |
14-04-2024 21:26:56 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 10 11 12 13 14 15 18 23 25 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 21:26:27 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 20:53:53 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 20:51:43 | 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; |
14-04-2024 20:35:46 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 20:33:34 | 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; |
14-04-2024 20:30:43 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 20:28:58 | 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; |
14-04-2024 20:15:43 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 20:13:43 | 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; |
14-04-2024 20:10:31 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 20:08:43 | 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; |
14-04-2024 20:00:23 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-04-2024 19:58:34 | 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; |
2 weeks ago
The variation of over 8dB in downstream signal levels shows there is something seriously wrong with the connection.
It might be something a simple as a poor coax connection, so they are worth checking. Otherwise it's going to need a serious check from the cabinet.
2 weeks ago
see if it downstream or upstream
Packet Loss Test – Test Your Connection Quality
Packet Loss Test - Test Your Connection Online | DeviceTests