on 02-11-2022 19:20
Hi can someone tell me if my qam is wrong please?. My upload qam is always 64 as is everyone's I have 1 channel 32qam and 2 at 16qam I think 64 symbols is more data than 16 no?
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 43100000 | 41.3 | 5120 KSym/sec | 32QAM | 2 |
2 | 30100000 | 40.8 | 5120 KSym/sec | 16QAM | 4 |
3 | 36600000 | 41 | 5120 KSym/sec | 16QAM | 3 |
4 | 49600000 | 41.5 | 5120 KSym/sec | 64QAM | 1 |
5 | 23600000 | 40 | 5120 KSym/sec | 64QAM | 5 |
Answered! Go to Answer
on 06-09-2023 19:02
Upstream is right on the edge, Viper - as I'm sure you know. It's taking 50+ dBmv power for the CMTS to be able to read at 16QAM. Right on the edge.
With regard to the BQM graphs, they may be doing area work at night that they can't be bothered to tell you about.
on 07-09-2023 11:45
No they are not doing any work mate as its been like this since I started the bqm when she first rang about her tv always freezing, infact it's usually worse I've uploaded some. When I got time after the end of the week I'm going to contact which and ofcom as our treatment has been diabolical, and the lack of knowledge from the people involved is unreal. They should hire people like you who don't need the best part of a year to find a simple and obvious problem. I've gave them so many chances and they spit in our faces time and time again, just trying to waste time and hope it magically fixes itself. They need to be held accountable for there terrible treatment of customers.
Regards
on 09-09-2023 13:07
Hey @Viper-t,
Thanks for getting back to us, sorry that this is still ongoing for you.
After checking into our systems I see no issues which would be directly affecting you, with regards to the BQM graph, can you confirm if you have had any texts as of late confirming work being done in your area?
Joe
on 10-09-2023 14:40
I'll tell you shall I what's wrong our end as your end is in a book/script. My parents TV freezes all the time so you sent an engineer who rang networks and confirmed on AUDIO TAPE as always, as VIRGIN MEDIA are now all the time LYING TO CUSTOMERS. confirmed area snr problem South bristol since then they have done squat, did not start a ticket and did not catch up with my elderly parents. Then you send another engineer a more useless one who installed a hub 5 even though they are on m125 fair enough, he also confirmed as bristol cables are all in trenches they are to old and fail. I wonder if that might be our problem? The router is not in spec all upstream modulations are maxed out power wise and all qams are 16qam and the netlog is filled with the most serious critical error SYNC Timing Synchronization failure - Loss of Sync which mean it can't talk to the cmts every 20ms so not synchronised so can lose connection and has to restart/renegotiate again, the amount EVERYDAY. tv continues to freeze lag pixelates. Others of us locally continue to have noise problems, I had another dropout last night but that's why I'm now suing your a€€ and reporting you to which as you just refuse to do anything.
10-09-2023 09:56:28 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
10-09-2023 09:56:24 | 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; |
10-09-2023 09:56:19 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-09-2023 09:56:06 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-09-2023 09:56:04 | notice | Honoring MDD; IP provisioning mode = IPv4 |
10-09-2023 09:55:52 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-09-2023 09:55:41 | critical | Cable Modem Reboot via RG reboot command |
09-09-2023 09:53:30 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 09:53:19 | critical | Cable Modem Reboot via RG reboot command |
08-09-2023 10:01:55 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-09-2023 10:01:43 | critical | Cable Modem Reboot via RG reboot command |
07-09-2023 10:26:42 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-09-2023 10:26:31 | critical | Cable Modem Reboot via RG reboot command |
06-09-2023 10:08:33 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
06-09-2023 10:08:21 | critical | Cable Modem Reboot via RG reboot command |
03-09-2023 09:56:55 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
03-09-2023 09:56:44 | critical | Cable Modem Reboot via RG reboot command |
02-09-2023 10:44:29 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-09-2023 10:44:18 | critical | Cable Modem Reboot via RG reboot command |
01-09-2023 09:24:25 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-09-2023 09:24:13 | critical | Cable Modem Reboot via RG reboot command |
31-08-2023 01:38:18 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-08-2023 01:38:18 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-08-2023 01:37:11 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-08-2023 23:07:49 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-08-2023 23:07:38 | critical | Cable Modem Reboot via RG reboot command |
30-08-2023 23:05:41 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-08-2023 15:34:53 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-08-2023 15:34:41 | critical | Cable Modem Reboot due to SW Upgrade |
30-08-2023 15:29:41 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-08-2023 15:29:29 | critical | Cable Modem Reboot via RG reboot command |
30-08-2023 15:27:17 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 10-09-2023 17:13
Also why is the t4 (16 consecutive t3 timeouts) error while trying to range upstream channel 8? There isnt a channel 8 only 4 on docsis 3.0. The modem has power and Ranging issues as well as daily dropped connections. My parents need the engineer to set this up correctly as its still not fixed the reason they were there to fix the TV from cutting out and freezing. Which hub 5 will not do. Todays, in the day latency below showing the area problem noise as always.
Upstream bonded channels
0 | 49600000 | 49.8 | 5120 | QAM 16 | 1 |
1 | 43100000 | 49.8 | 5120 | QAM 16 | 2 |
2 | 36600000 | 49.8 | 5120 | QAM 16 | 3 |
3 | 30100000 | 49.5 | 5120 | QAM 16 | 4 |
4 | 23600000 | 49.8 | 5120 | QAM 16 | 5 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 14-09-2023 17:24
Will you fix my parents tv/connection?
0 | 49600000 | 49.5 | 5120 | QAM 16 | 1 |
1 | 43100000 | 49.3 | 5120 | QAM 16 | 2 |
2 | 36600000 | 49.3 | 5120 | QAM 16 | 3 |
3 | 30100000 | 49.3 | 5120 | QAM 16 | 4 |
4 | 23600000 | 49.3 | 5120 | QAM 16 | 5 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
4-09-2023 17:25:49 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-09-2023 09:18:19 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
14-09-2023 09:18:16 | 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; |
14-09-2023 09:18:11 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-09-2023 09:17:59 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-09-2023 09:17:56 | notice | Honoring MDD; IP provisioning mode = IPv4 |
14-09-2023 09:17:46 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-09-2023 09:17:35 | critical | Cable Modem Reboot via RG reboot command |
13-09-2023 09:12:35 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
13-09-2023 09:12:23 | critical | Cable Modem Reboot via RG reboot command |
12-09-2023 10:13:06 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-09-2023 10:12:55 | critical | Cable Modem Reboot via RG reboot command |
11-09-2023 09:45:44 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-09-2023 09:45:33 | critical | Cable Modem Reboot via RG reboot command |
10-09-2023 09:55:52 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-09-2023 09:55:41 | critical | Cable Modem Reboot via RG reboot command |
09-09-2023 09:53:30 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 09:53:19 | critical | Cable Modem Reboot via RG reboot command |
08-09-2023 10:01:55 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-09-2023 10:01:43 | critical | Cable Modem Reboot via RG reboot command |
07-09-2023 10:26:42 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
07-09-2023 10:26:31 | critical | Cable Modem Reboot via RG reboot command |
06-09-2023 10:08:33 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
06-09-2023 10:08:21 | critical | Cable Modem Reboot via RG reboot command |
03-09-2023 09:56:55 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
03-09-2023 09:56:44 | critical | Cable Modem Reboot via RG reboot command |
02-09-2023 10:44:29 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-09-2023 10:44:18 | critical | Cable Modem Reboot via RG reboot command |
01-09-2023 09:24:25 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-09-2023 09:24:13 | critical | Cable Modem Reboot via RG reboot command |
31-08-2023 01:38:18 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-08-2023 01:38:18 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 14-09-2023 17:36
All these critical errors are a serious problem, all upstream modulations have dropped and stay at 16 qam as the network is TOO NOISY causing there tv to lose picture pixelate freeze, power is maxed on upstream. Bqm shows terrible latency causing these problems hub 5 is worse than there hub3 why does virgin media make problems worse? Is this retaliation for complaining? As there is so many times across your forum where this is the case, can someone do there job as there to old for this stress or I will add there case to mine and will be a way bigger problem than it needs to be. As this terrible service has gone on to long. Just read your forums or ofcom who ever do not care is making a once great company terrible, what a waste.
on 16-09-2023 17:58
Thanks for your reply, I have checked our system and can see there were some connection drops over the past few days. But they look like they have been resolved now.
How are things looking at your end? If you are still seeing issues, please reboot the Hub. If the issues continue after the reboot, please let us know. We're always happy to assist.
Regards
Nathan
The do's and don'ts. Keep the community welcoming for all. Follow the house rules
on 17-09-2023 16:35
Hi Nathan, Done a reset think it updated firmware but the problem persists, netlog filled straight away 2 loss of syncs with cmts, failed to aquire modulation timing, and reboots like the pages before. I've looked in the forums a lot of people with a hub 5 upgrade/downgrade is having problems. My parents problem and other's locally have an area problem I told the engineer a hub 5 will do nothing to fix the noise or hide it. I also mentioned it would probably make it worse, but he was adamant it would improve there tv freezing crashing. Its the same problem as the thread hub 5 dropping docsis connection. There tv froze again last night she tells me around 9pm looking at the bqm chart which I've showed vm is full of latency everyday, upstream has dropped modulations 24 hours a day since the hub 5 was added before it was a few channels dropped now all of them this problem needs an engineer to fix but actually fix this time not make it worse. Upstream power maxed at dropped modulation. I'm shocked at what is happening at vm right now to all long term customers from the 90s unreal.
For transparency the drop at 310pm is from the reboot done as requested by vm.
0 | 49600000 | 49.3 | 5120 | QAM 32 | 1 |
1 | 43100000 | 49 | 5120 | QAM 32 | 2 |
2 | 36600000 | 49 | 5120 | QAM 32 | 3 |
3 | 30100000 | 49 | 5120 | QAM 32 | 4 |
4 | 23600000 | 49 | 5120 | QAM 32 | 5 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
Downstream bonded channels
1 | 331000000 | 7.2 | 41 | QAM 256 | 25 |
2 | 139000000 | 3.9 | 40 | QAM 256 | 1 |
3 | 147000000 | 4.1 | 40 | QAM 256 | 2 |
4 | 155000000 | 4.1 | 40 | QAM 256 | 3 |
5 | 163000000 | 4.2 | 40 | QAM 256 | 4 |
6 | 171000000 | 4.6 | 41 | QAM 256 | 5 |
7 | 179000000 | 4.8 | 41 | QAM 256 | 6 |
8 | 187000000 | 4.9 | 41 | QAM 256 | 7 |
9 | 195000000 | 5.3 | 41 | QAM 256 | 8 |
10 | 203000000 | 5.4 | 41 | QAM 256 | 9 |
11 | 211000000 | 5.8 | 41 | QAM 256 | 10 |
12 | 219000000 | 5.9 | 41 | QAM 256 | 11 |
13 | 227000000 | 6 | 41 | QAM 256 | 12 |
14 | 235000000 | 6.2 | 41 | QAM 256 | 13 |
15 | 243000000 | 6.1 | 41 | QAM 256 | 14 |
16 | 251000000 | 6 | 41 | QAM 256 | 15 |
17 | 259000000 | 6 | 41 | QAM 256 | 16 |
18 | 267000000 | 6.1 | 41 | QAM 256 | 17 |
19 | 275000000 | 6.3 | 41 | QAM 256 | 18 |
20 | 283000000 | 6.6 | 41 | QAM 256 | 19 |
21 | 291000000 | 6.8 | 41 | QAM 256 | 20 |
22 | 299000000 | 6.8 | 41 | QAM 256 | 21 |
23 | 307000000 | 6.9 | 41 | QAM 256 | 22 |
24 | 315000000 | 7.1 | 41 | QAM 256 | 23 |
25 | 323000000 | 7.2 | 41 | QAM 256 | 24 |
26 | 339000000 | 7.3 | 41 | QAM 256 | 26 |
27 | 347000000 | 7.4 | 41 | QAM 256 | 27 |
28 | 355000000 | 7.4 | 41 | QAM 256 | 28 |
29 | 363000000 | 7.5 | 41 | QAM 256 | 29 |
30 | 371000000 | 7.4 | 41 | QAM 256 | 30 |
31 | 379000000 | 7.4 | 40 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 41 | 0 | 0 |
2 | Locked | 40 | 0 | 0 |
3 | Locked | 40 | 0 | 0 |
4 | Locked | 40 | 0 | 0 |
5 | Locked | 40 | 0 | 0 |
6 | Locked | 41 | 0 | 0 |
7 | Locked | 41 | 0 | 0 |
8 | Locked | 41 | 0 | 0 |
9 | Locked | 41 | 0 | 0 |
10 | Locked | 41 | 0 | 0 |
11 | Locked | 41 | 0 | 0 |
12 | Locked | 41 | 0 | 0 |
13 | Locked | 41 | 0 | 0 |
14 | Locked | 41 | 0 | 0 |
15 | Locked | 41 | 0 | 0 |
16 | Locked | 41 | 0 | 0 |
17 | Locked | 41 | 0 | 0 |
18 | Locked | 41 | 0 | 0 |
19 | Locked | 41 | 0 | 0 |
20 | Locked | 41 | 0 | 0 |
21 | Locked | 41 | 0 | 0 |
22 | Locked | 41 | 0 | 0 |
23 | Locked | 41 | 0 | 0 |
24 | Locked | 41 | 0 | 0 |
25 | Locked | 41 | 0 | 0 |
26 | Locked | 41 | 0 | 0 |
27 | Locked | 41 | 0 | 0 |
28 | Locked | 41 | 0 | 0 |
29 | Locked | 41 | 0 | 0 |
30 | Locked | 41 | 0 | 0 |
31 | Locked | 40 | 0 | 0 |
17-09-2023 17:16:49 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
17-09-2023 17:16:45 | 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; |
17-09-2023 17:16:40 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-09-2023 17:16:27 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-09-2023 17:16:25 | notice | Honoring MDD; IP provisioning mode = IPv4 |
17-09-2023 17:16:02 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-09-2023 17:15:50 | critical | Cable Modem Reboot via RG reboot command |
17-09-2023 17:13:02 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-09-2023 17:12:50 | critical | Cable Modem reset to Factory Default via reset button |
on 17-09-2023 16:40
By the way the netlog time is wrong when logged in properly it's still wrong, obviously can't get real time from cmts?