on 02-01-2022 02:06
Hi Everyone,
So I have a hub4 in modem mode connected to my Netgear Nighthawk R9000 (via a Cat 8.1 Cable). Since upgrading to 1gb I had a few teething problems, but I've had a SOLID 930 download and 52 upload since the summer (tested at the router via the software built into the Nighthawk Router).
Since early December my speeds have dropped to between 400-700, and never get anywhere near to 900 (upload is still sold at 52).
I have gone round and round in circles to the helpline, rebooting etc etc. but it isn't getting me anywhere. I asked if this could be realted to my neighbour getting virgin installed at around the same time but they said not... and they say everything on my service is good.
Any suggestions...Below is an extract from the network log + status, if anyone knowledgable can spot any issues.
Answered! Go to Answer
on 02-01-2022 07:15
Network log confirms the poor connection, and the numbers show your downstream power levels need attention. I'll mark that for staff to advise and book a technician as appropriate.
on 02-01-2022 02:07
Time Priority Description
Wed 01/12/2021 09:45:16 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:21 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:22 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:22 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:23 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:23 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:24 | 6 | CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; 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; |
Wed 01/12/2021 09:45:27 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:29 | 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; |
Wed 01/12/2021 09:45:40 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:46 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:45:47 | 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; |
Wed 01/12/2021 09:46:44 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:47:03 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:51:48 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:51:48 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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; |
Wed 01/12/2021 09:51:48 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:51:54 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:52:01 | 6 | CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; 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; |
Wed 01/12/2021 09:52:44 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:52:45 | 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; |
Wed 01/12/2021 09:52:47 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 01/12/2021 09:52:58 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 03/12/2021 15:32:39 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 03/12/2021 15:54:54 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 04/12/2021 04:20:27 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 04/12/2021 04:28:43 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 07/12/2021 08:20:57 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 07/12/2021 08:50:42 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 10/12/2021 20:20:57 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 10/12/2021 20:44:49 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/12/2021 03:55:24 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/12/2021 04:26:52 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 14/12/2021 08:20:58 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 14/12/2021 08:49:26 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 15/12/2021 01:04:41 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 15/12/2021 01:08:33 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 17/12/2021 20:20:58 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 17/12/2021 20:26:15 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/12/2021 13:25:57 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:20 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/12/2021 01:30:20 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 21/12/2021 10:54:16 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 22/12/2021 10:55:40 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/12/2021 17:10:16 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 25/12/2021 10:08:26 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 25/12/2021 12:42:43 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 28/12/2021 22:08:27 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 02-01-2022 02:08
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13 | 458250000 | 10.1 | 39 | QAM256 | 13 |
1 | 362250000 | 11.1 | 38.6 | QAM256 | 1 |
2 | 370250000 | 11.4 | 38.6 | QAM256 | 2 |
3 | 378250000 | 11.6 | 38.6 | QAM256 | 3 |
4 | 386250000 | 11.6 | 39 | QAM256 | 4 |
5 | 394250000 | 11.1 | 38.6 | QAM256 | 5 |
6 | 402250000 | 10.8 | 38.6 | QAM256 | 6 |
7 | 410250000 | 10.8 | 38.6 | QAM256 | 7 |
8 | 418250000 | 10.8 | 39 | QAM256 | 8 |
9 | 426250000 | 10.8 | 39 | QAM256 | 9 |
10 | 434250000 | 10.2 | 39 | QAM256 | 10 |
11 | 442250000 | 10.2 | 39 | QAM256 | 11 |
12 | 450250000 | 9.7 | 38.6 | QAM256 | 12 |
14 | 466250000 | 9.9 | 39 | QAM256 | 14 |
15 | 474250000 | 9.7 | 39 | QAM256 | 15 |
16 | 482250000 | 9.3 | 38.6 | QAM256 | 16 |
17 | 490250000 | 10 | 38.6 | QAM256 | 17 |
18 | 498250000 | 9.9 | 39 | QAM256 | 18 |
19 | 506250000 | 10 | 39 | QAM256 | 19 |
20 | 514250000 | 9.5 | 38.6 | QAM256 | 20 |
21 | 522250000 | 10 | 39 | QAM256 | 21 |
22 | 530250000 | 9.6 | 39 | QAM256 | 22 |
23 | 538250000 | 10.1 | 39 | QAM256 | 23 |
24 | 546250000 | 9.9 | 39 | QAM256 | 24 |
25 | 554250000 | 10.1 | 38.6 | QAM256 | 25 |
26 | 562250000 | 9.2 | 39 | QAM256 | 26 |
27 | 570250000 | 9.4 | 38.6 | QAM256 | 27 |
28 | 578250000 | 10 | 39 | QAM256 | 28 |
29 | 586250000 | 9.9 | 38.6 | QAM256 | 29 |
30 | 594250000 | 9.4 | 38.6 | QAM256 | 30 |
31 | 602250000 | 9 | 38.6 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
13 | Locked | 38.983261 | 0 | 0 |
1 | Locked | 38.605377 | 0 | 0 |
2 | Locked | 38.605377 | 0 | 0 |
3 | Locked | 38.605377 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.605377 | 0 | 0 |
6 | Locked | 38.605377 | 0 | 0 |
7 | Locked | 38.605377 | 0 | 0 |
8 | Locked | 38.983261 | 0 | 0 |
9 | Locked | 38.983261 | 0 | 0 |
10 | Locked | 38.983261 | 0 | 0 |
11 | Locked | 38.983261 | 7 | 0 |
12 | Locked | 38.605377 | 0 | 0 |
14 | Locked | 38.983261 | 0 | 0 |
15 | Locked | 38.983261 | 0 | 0 |
16 | Locked | 38.605377 | 0 | 0 |
17 | Locked | 38.605377 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 38.605377 | 0 | 0 |
21 | Locked | 38.983261 | 0 | 0 |
22 | Locked | 38.983261 | 0 | 0 |
23 | Locked | 38.983261 | 0 | 0 |
24 | Locked | 38.983261 | 0 | 0 |
25 | Locked | 38.605377 | 0 | 0 |
26 | Locked | 38.983261 | 0 | 0 |
27 | Locked | 38.605377 | 0 | 0 |
28 | Locked | 38.983261 | 8 | 0 |
29 | Locked | 38.605377 | 6 | 0 |
30 | Locked | 38.605377 | 0 | 0 |
31 | Locked | 38.605377 | 0 | 0 |
33 | 96 | 4K | 1880 | QAM4096 | 728 |
33 | Locked | 40 | 9.9 | 1137477 | 0 |
on 02-01-2022 07:15
Network log confirms the poor connection, and the numbers show your downstream power levels need attention. I'll mark that for staff to advise and book a technician as appropriate.
on 02-01-2022 08:36
Hi @amithadm,
Welcome to our Community Forums and thanks for your post.
I'm sorry to hear you've been having some issues with the service. I've ran some tests and can see your downstream power levels are of specification so will need to book a technician visit for you so these can be corrected.
Will pop you a PM now to confirm some details.
Thanks
on 02-01-2022 10:05
Thanks for confirming the requested details via PM @smithadm
I've booked a technician for you to come out and have a look into the issue with your power levels. You can find confirmation of the visit via your online account.
Please let me know if there are any problems with the date or time and I can look to reschedule this for you. In regards to the appointment there are some details you need to know about. There will be no charge for this visit unless:
•The technician diagnoses the faults as not being caused by our network/equipment
•The technician discovers that the fault or problem relates to your equipment
•The technician discovers that the fault or problem relates to any system that we are not responsible for
The technician will confirm during their visit if any of these instances apply, and if so, a £25 charge will be applied to your account.
Please ensure there is someone over the age of 18 present at the time of the visit. If you need to change or cancel your appointment you can also do this online or via the MyVM app by 4pm the day before the appointment.
If you do miss an agreed appointment for any reason, a £25 missed appointment charge will be applied to your account on the day of the appointment.
Let us know how the visit goes!
on 19-02-2022 02:05
I have been having issues for almost 12 months and running out of patience. Below is the test speeds completed on speedtest as recommended by Virgin over last 12 months. I have shut down and restarted several times and most of the time I am below 50% but funny thing is that my upload speeds are nearly always over 50.
I have a cat 8 cable and and a hub 4 router. So the question is why am i paying for a 1gb line?
I have also post the Downstream, Upstream and Network log as requested
Hope you can let me know why my speeds are low
on 19-02-2022 02:12
20 | 291000000 | 1.9 | 39 | QAM256 | 20 |
1 | 139000000 | 3.5 | 38.6 | QAM256 | 1 |
2 | 147000000 | 3.2 | 39 | QAM256 | 2 |
3 | 155000000 | 3 | 39 | QAM256 | 3 |
4 | 163000000 | 2.9 | 38.6 | QAM256 | 4 |
5 | 171000000 | 2.7 | 39 | QAM256 | 5 |
6 | 179000000 | 2.8 | 38.6 | QAM256 | 6 |
7 | 187000000 | 2.4 | 39 | QAM256 | 7 |
8 | 195000000 | 2.4 | 39 | QAM256 | 8 |
9 | 203000000 | 2.4 | 40.4 | QAM256 | 9 |
10 | 211000000 | 2.3 | 38.6 | QAM256 | 10 |
11 | 219000000 | 2 | 39 | QAM256 | 11 |
12 | 227000000 | 1.9 | 39 | QAM256 | 12 |
13 | 235000000 | 1.7 | 38.6 | QAM256 | 13 |
14 | 243000000 | 1.4 | 39 | QAM256 | 14 |
15 | 251000000 | 1.4 | 39 | QAM256 | 15 |
16 | 259000000 | 0.7 | 39 | QAM256 | 16 |
17 | 267000000 | 0.7 | 39 | QAM256 | 17 |
18 | 275000000 | 1.2 | 39 | QAM256 | 18 |
19 | 283000000 | 1.8 | 39 | QAM256 | 19 |
21 | 299000000 | 1.6 | 40.4 | QAM256 | 21 |
22 | 307000000 | 1.3 | 39 | QAM256 | 22 |
23 | 315000000 | 1.5 | 39 | QAM256 | 23 |
24 | 323000000 | 1.5 | 39 | QAM256 | 24 |
25 | 331000000 | 0.8 | 39 | QAM256 | 25 |
26 | 339000000 | 1 | 39 | QAM256 | 26 |
27 | 347000000 | 1.3 | 39 | QAM256 | 27 |
28 | 355000000 | 1.2 | 39 | QAM256 | 28 |
29 | 363000000 | 1.2 | 39 | QAM256 | 29 |
30 | 371000000 | 1.2 | 39 | QAM256 | 30 |
31 | 379000000 | 0.9 | 39 | QAM256 | 31 |
20 | Locked | 38.983261 | 0 | 0 |
1 | Locked | 38.605377 | 0 | 0 |
2 | Locked | 38.983261 | 0 | 0 |
3 | Locked | 38.983261 | 0 | 0 |
4 | Locked | 38.605377 | 0 | 0 |
5 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 38.605377 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 38.983261 | 0 | 0 |
9 | Locked | 40.366287 | 0 | 0 |
10 | Locked | 38.605377 | 0 | 0 |
11 | Locked | 38.983261 | 0 | 0 |
12 | Locked | 38.983261 | 0 | 0 |
13 | Locked | 38.605377 | 0 | 0 |
14 | Locked | 38.983261 | 0 | 0 |
15 | Locked | 38.983261 | 0 | 0 |
16 | Locked | 38.983261 | 0 | 0 |
17 | Locked | 38.983261 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 38.983261 | 0 | 0 |
23 | Locked | 38.983261 | 0 | 0 |
24 | Locked | 38.983261 | 0 | 0 |
25 | Locked | 38.983261 | 0 | 0 |
26 | Locked | 38.983261 | 0 | 0 |
27 | Locked | 38.983261 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 38.983261 | 0 | 0 |
31 | Locked | 38.983261 | 0 | 0 |
on 19-02-2022 02:13
1 | 39400000 | 46.3 | 5120 KSym/sec | 64QAM | 4 |
2 | 53700000 | 45.5 | 5120 KSym/sec | 64QAM | 2 |
3 | 60300000 | 45.5 | 5120 KSym/sec | 64QAM | 1 |
4 | 46200000 | 45.8 | 5120 KSym/sec | 64QAM | 3 |
1 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
on 19-02-2022 02:13
Wed 22/12/2021 05:44:34 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 22/12/2021 07:32:35 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 25/12/2021 17:44:34 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 25/12/2021 21:38:39 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 27/12/2021 03:54:25 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 27/12/2021 12:19:04 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 29/12/2021 05:44:34 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 29/12/2021 09:39:59 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 01/01/2022 17:44:34 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 01/01/2022 21:26:18 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 05/01/2022 05:44:34 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 05/01/2022 18:40:26 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 08/01/2022 17:44:34 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 09/01/2022 17:47:07 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:22 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 10/01/2022 00:23:02 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 10/01/2022 16:56:00 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 10/01/2022 21:25:46 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 11/01/2022 10:00:47 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 13/01/2022 07:35:12 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 13/01/2022 16:29:27 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 15/01/2022 16:42:14 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 15/01/2022 18:29:31 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 16/01/2022 07:10:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 16/01/2022 10:42:50 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 19/01/2022 19:10:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 19/01/2022 22:28:49 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 23/01/2022 07:10:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 23/01/2022 15:12:27 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 26/01/2022 15:50:40 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 26/01/2022 16:06:00 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 26/01/2022 19:10:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 26/01/2022 20:27:57 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 30/01/2022 07:10:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 31/01/2022 13:37:39 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 02/02/2022 19:10:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 02/02/2022 21:04:56 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 06/02/2022 07:10:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 06/02/2022 20:24:41 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 09/02/2022 19:10:03 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |