on 12-07-2021 23:11
Hi all
Long-term VM customer. Recently started having the dreaded RCS Partial Service and Loss of Sync around 6 to 8 weeks ago. I have made numerous calls, had an engineer out to check the connection to my home, had two engineer callouts to check two cabinets in the street which have both had some form of upgrade.
My friend in the street is also having the same level of dropouts I am, but at different times of the day.
I am due to receive another callback from their head office on Thursday. I am hoping that someone might have some sort of idea into what might be causing these issues given I have had engineers check my home, and the two cabinets in the street, and that my friend has the same problem on the same cabinet connections.
I've registered with thinkbroadband to setup one of those graphs and will post this when I get 24 hours worth of data.
Anyway, here's the router stats:
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz) | 331000000 | Locked |
Ranged Upstream Channel (Hz) | 60300292 | Locked |
Time Priority Description
12/07/2021 21:24:33 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 21:22:59 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 18:49:1 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 18:49:1 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 17:01:0 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 17:01:0 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 12:59:39 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 12:59:5 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 11:26:56 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:02:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 09:55:42 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 09:53:40 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 09:53:36 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 09:53:36 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 09:53:35 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 09:21:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 09:17:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 08:39:19 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 08:39:19 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/07/2021 06:21:37 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 12-07-2021 23:11
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 5 | 38 | 256 qam | 25 |
2 | 203000000 | 3.7 | 38 | 256 qam | 9 |
3 | 211000000 | 3.7 | 38 | 256 qam | 10 |
4 | 219000000 | 3.9 | 38 | 256 qam | 11 |
5 | 227000000 | 3.7 | 38 | 256 qam | 12 |
6 | 235000000 | 4 | 38 | 256 qam | 13 |
7 | 243000000 | 3.9 | 38 | 256 qam | 14 |
8 | 251000000 | 4 | 38 | 256 qam | 15 |
9 | 259000000 | 4.1 | 38 | 256 qam | 16 |
10 | 267000000 | 4.5 | 38 | 256 qam | 17 |
11 | 275000000 | 4.4 | 38 | 256 qam | 18 |
12 | 283000000 | 4.5 | 38 | 256 qam | 19 |
13 | 291000000 | 4.6 | 38 | 256 qam | 20 |
14 | 299000000 | 5.1 | 38 | 256 qam | 21 |
15 | 307000000 | 5.1 | 38 | 256 qam | 22 |
16 | 315000000 | 5.1 | 38 | 256 qam | 23 |
17 | 323000000 | 5 | 37 | 256 qam | 24 |
18 | 339000000 | 4.9 | 38 | 256 qam | 26 |
19 | 347000000 | 4.9 | 38 | 256 qam | 27 |
20 | 355000000 | 5 | 38 | 256 qam | 28 |
21 | 363000000 | 4.9 | 38 | 256 qam | 29 |
22 | 371000000 | 4.8 | 38 | 256 qam | 30 |
23 | 379000000 | 4.8 | 38 | 256 qam | 31 |
24 | 387000000 | 4.8 | 38 | 256 qam | 32 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 312 | 3456 |
2 | Locked | 38.6 | 305 | 3499 |
3 | Locked | 38.6 | 328 | 3311 |
4 | Locked | 38.9 | 300 | 3215 |
5 | Locked | 38.6 | 322 | 3353 |
6 | Locked | 38.6 | 287 | 3582 |
7 | Locked | 38.6 | 275 | 3377 |
8 | Locked | 38.6 | 269 | 3410 |
9 | Locked | 38.6 | 278 | 3368 |
10 | Locked | 38.6 | 297 | 3522 |
11 | Locked | 38.6 | 303 | 3307 |
12 | Locked | 38.6 | 291 | 3033 |
13 | Locked | 38.6 | 322 | 3140 |
14 | Locked | 38.6 | 296 | 3235 |
15 | Locked | 38.9 | 297 | 3315 |
16 | Locked | 38.6 | 309 | 2936 |
17 | Locked | 37.6 | 338 | 3117 |
18 | Locked | 38.6 | 326 | 3231 |
19 | Locked | 38.6 | 312 | 3298 |
20 | Locked | 38.6 | 302 | 3430 |
21 | Locked | 38.9 | 317 | 3138 |
22 | Locked | 38.6 | 298 | 2844 |
23 | Locked | 38.6 | 319 | 3020 |
24 | Locked | 38.6 | 287 | 2808 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 60300292 | 46.5 | 5120 | 64 qam | 1 |
2 | 46200000 | 45.5 | 5120 | 64 qam | 3 |
3 | 53700000 | 45.8 | 5120 | 64 qam | 2 |
4 | 39400000 | 45 | 5120 | 64 qam | 4 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 13-07-2021 06:50
on 13-07-2021 13:02
on 15-07-2021 15:04
Still not resolved:
Network Log
Time Priority Description
15/07/2021 13:55:14 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 13:45:32 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 13:33:44 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 12:55:32 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 09:56:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 09:56:5 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 09:12:22 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 09:12:22 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 06:19:29 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 05:52:45 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 05:25:22 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 05:11:34 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 04:52:14 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 04:52:14 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 00:15:14 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 00:07:18 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/07/2021 20:42:10 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/07/2021 20:00:58 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/07/2021 08:11:57 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/07/2021 08:07:16 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 15-07-2021 15:08
on 15-07-2021 15:14
Hi OfficialPerky,
Thanks for posting about this issue with your broadband on our forums, I am sorry you're having this problem which is causing some frustration for you!
I have already checked your services and can see you have an open complaint with the CEO complaints team about this, they are dealing with it on their end and have spoken to you today.
As a team that has more jurisdiction than us is already dealing with it, I feel it would be best to let them handle things in order to avoid any confusion or mixed messages from both teams.
I can see they are actively investigating this issue for you and will be continuing to keep in touch.
I wish you the best of luck with this. Please keep in mind that if they come to a resolution and you do not want to agree to it, you can ask to escalate your case. For more information about what this means and where it might go, please have a read of our complaints ownership process here.
Thanks,
Megan_L
16-08-2021 18:03 - edited 16-08-2021 18:09
Update for anyone interested.
Four engineers in total have either visited my premises or the cabinet outside. The last set of engineers, an area manager and his colleague, saw a high spike in dB at the front end of my property, it was way too high. A new Hub 4.0 has been provided, a new cable from cab to house has been replaced, which required digging up the pavement, and I am still getting the same issue, albeit at a reduced level. You can see it on the live graph attached. The spikes cause major latency and slow-down for a minute or so. There are also packet drops as well which has reduced from 9/10 times a day down to 4/5. In my initial post, those spikes in the graph below were appearing all through the 24 hours, now it looks much better but still getting dropouts.
I have since remembered there was scheduled maintenance in my area on May 17th of this year, coincidentally, the same time my problem began. After advising the area manager and the executive complaints team, they escalated it to Networks who have since been unable to find a fault, despite it being pinpointed to their maintenance works in May. This issue is also affecting other Virgin Media customers in my street but the level of disconnection is so minor mixed with different usage habits of neighbours, not enough reports have gone to VM for it to be considered an area fault.
I find the response frustrating. How can I sit here and accept that "maintenance" work which caused the problem cannot be resolved by the same people that caused it in the first place? The fact it was absolutely pinpoint perfect before the maintenance work, to now be told this cannot be resolved any further is deflating. Not sure whether to take it further than executive complaints or not given networks have basically shut me down.
I find it even more frustrating that my neighbours in the street will all have to ring in about the fault, ask for new hubs, ask for old cables to be dug out of the pavement and new ones put in, etc. just to get a level of improvement as I have.
Maddening.
on 18-08-2021 18:59
Thanks for coming back to us - OfficialPerky
I can see you've spoke to the team since posting and the agent dealing with your complaint.
They've chased networks for an update and will be in touch with you soon.
Kind regards,
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill
on 22-09-2021 20:32
LOOK AT THE STATE OF THAT THINKBROADBAND QUALITY MONITOR!
Here are my recent logs:
Network Log
Time Priority Description
Sun 19/09/2021 04:55:36 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; 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; |
Sun 19/09/2021 08:54:32 | 5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/09/2021 08:56:53 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; 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; |
Sun 19/09/2021 11:47:06 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/09/2021 11:47:21 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; 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; |
Sun 19/09/2021 16:08:54 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/09/2021 16:09:20 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; 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; |
Sun 19/09/2021 18:58:04 | 5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/09/2021 19:03:09 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; 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; |
Sun 19/09/2021 19:52:35 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/09/2021 19:53:05 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; 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; |
Sun 19/09/2021 23:40:42 | 5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 00:12:27 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; 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; |
Mon 20/09/2021 01:33:51 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 01:34:07 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; 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; |
Mon 20/09/2021 01:37:04 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 01:37:23 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 29; 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; |
Mon 20/09/2021 08:02:53 | 5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 08:13:23 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 29; 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; |
Mon 20/09/2021 08:26:30 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 08:26:53 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; 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; |
Mon 20/09/2021 11:20:48 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 11:21:13 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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; |
Mon 20/09/2021 12:42:18 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 12:45:18 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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; |
Mon 20/09/2021 13:19:10 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 13:19:37 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 27; 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; |
Mon 20/09/2021 19:06:49 | 5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 19:14:22 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 11; 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; |
Mon 20/09/2021 23:55:14 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/09/2021 23:55:16 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 11; 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; |
Tue 21/09/2021 00:39:00 | 5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 21/09/2021 01:19:32 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; 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; |
Tue 21/09/2021 06:26:41 | 5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 21/09/2021 06:33:14 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; 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; |
Tue 21/09/2021 12:34:26 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 21/09/2021 12:34:29 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 21/09/2021 12:34:43 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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; |
Tue 21/09/2021 15:25:18 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 21/09/2021 15:25:20 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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; |
Tue 21/09/2021 15:25:21 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 21/09/2021 15:47:51 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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; |