on 03-02-2023 13:21
Since around late January I've been noticing issues with gaming, having looked into this with some of the monitoring I've got setup I can see that since around the 23rd January I've been having consistency high latency throughout the day. I've been through what I suspect I'll get told to do by telephone support around testing and turning it off and on again to no avail. Can anyone advise how best to progress this with VM?
Modem Stats - HH5
Status
Cable Modem StatusItem Status Comments
Acquired Downstream Channel(Hz) | 331000000 | Locked |
Ranged Upstream Channel(Hz) | 46200000 | Ranged |
Provisioning State | Online | Operational |
Downstream
Downstream bonded channels
1 | 331000000 | -1.6 | 40 | QAM 256 | 25 |
2 | 163000000 | 0.1 | 41 | QAM 256 | 4 |
3 | 171000000 | 0.1 | 41 | QAM 256 | 5 |
4 | 179000000 | 0 | 41 | QAM 256 | 6 |
5 | 187000000 | 0.1 | 41 | QAM 256 | 7 |
6 | 195000000 | 0.1 | 41 | QAM 256 | 8 |
7 | 203000000 | 0.1 | 41 | QAM 256 | 9 |
8 | 211000000 | 0.3 | 41 | QAM 256 | 10 |
9 | 219000000 | 0.2 | 41 | QAM 256 | 11 |
10 | 227000000 | 0.1 | 41 | QAM 256 | 12 |
11 | 235000000 | 0.1 | 41 | QAM 256 | 13 |
12 | 243000000 | 0.4 | 41 | QAM 256 | 14 |
13 | 251000000 | 0.8 | 41 | QAM 256 | 15 |
14 | 259000000 | -1 | 41 | QAM 256 | 16 |
15 | 267000000 | -1.3 | 41 | QAM 256 | 17 |
16 | 275000000 | -1.4 | 41 | QAM 256 | 18 |
17 | 283000000 | -1.4 | 40 | QAM 256 | 19 |
18 | 291000000 | -1.4 | 40 | QAM 256 | 20 |
19 | 299000000 | -1.4 | 40 | QAM 256 | 21 |
20 | 307000000 | -1.5 | 40 | QAM 256 | 22 |
21 | 315000000 | -1.6 | 40 | QAM 256 | 23 |
22 | 323000000 | -1.6 | 40 | QAM 256 | 24 |
23 | 339000000 | -1.6 | 40 | QAM 256 | 26 |
24 | 347000000 | -1.7 | 40 | QAM 256 | 27 |
25 | 355000000 | -1.7 | 40 | QAM 256 | 28 |
26 | 363000000 | -1.6 | 40 | QAM 256 | 29 |
27 | 371000000 | -1.7 | 40 | QAM 256 | 30 |
28 | 379000000 | -1.7 | 40 | QAM 256 | 31 |
29 | 387000000 | -1.8 | 40 | QAM 256 | 32 |
30 | 395000000 | -1.9 | 40 | QAM 256 | 33 |
31 | 403000000 | -2 | 40 | QAM 256 | 34 |
Downstream bonded channels
1 | Locked | 40 | 0 | 0 |
2 | Locked | 41 | 5 | 0 |
3 | Locked | 41 | 1 | 0 |
4 | Locked | 41 | 0 | 0 |
5 | Locked | 41 | 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 | 5 | 0 |
14 | Locked | 41 | 7 | 0 |
15 | Locked | 41 | 3 | 0 |
16 | Locked | 41 | 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 | 40 | 1 | 0 |
28 | Locked | 40 | 0 | 0 |
29 | Locked | 40 | 1 | 0 |
30 | Locked | 40 | 0 | 0 |
31 | Locked | 40 | 0 | 0 |
Upstream
Upstream bonded channels
0 | 46200000 | 37.3 | 5120 | QAM 64 | 3 |
1 | 39400000 | 36.8 | 5120 | QAM 64 | 4 |
2 | 32600000 | 36.8 | 5120 | QAM 64 | 5 |
3 | 23600000 | 36.3 | 5120 | QAM 64 | 6 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 1 | 0 |
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 2 | 0 |
3 | ATDMA | 0 | 0 | 66 | 0 |
Log
Network Log
03-02-2023 00:07:58 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-02-2023 22:37:05 | warning | 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; |
02-02-2023 22:37:05 | warning | Dynamic Range Window violation |
01-02-2023 04:44:07 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-02-2023 00:31:50 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-01-2023 19:55:36 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-01-2023 18:54:01 | warning | 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; |
31-01-2023 18:54:01 | warning | Dynamic Range Window violation |
30-01-2023 03:56:45 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-01-2023 00:00:07 | warning | 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; |
30-01-2023 00:00:07 | warning | Dynamic Range Window violation |
29-01-2023 22:12:18 | warning | Dynamic Range Window violation |
29-01-2023 22:12:18 | warning | 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; |
29-01-2023 19:00:18 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-01-2023 18:53:18 | warning | Dynamic Range Window violation |
29-01-2023 18:53:18 | warning | 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; |
29-01-2023 03:52:23 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-01-2023 17:37:43 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
28-01-2023 17:37:37 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-01-2023 17:37:37 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-01-2023 17:37:37 | warning | Dynamic Range Window violation |
28-01-2023 17:37:37 | warning | Dynamic Range Window violation |
28-01-2023 17:37:36 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-01-2023 17:37:31 | 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; |
28-01-2023 17:37:28 | notice | TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-01-2023 17:37:25 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-01-2023 17:37:23 | notice | Honoring MDD; IP provisioning mode = IPv4 |
28-01-2023 17:37:13 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
28-01-2023 17:36:56 | critical | Cable Modem Reboot due to power button reset |
16-01-2023 17:34:31 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-01-2023 17:34:15 | critical | Cable Modem Reboot due to power button reset |
15-01-2023 13:15:32 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Answered! Go to Answer
04-02-2023 11:06 - edited 04-02-2023 11:07
You have an excessive amount of T3 timeouts and the BQM is pretty bad.
Your power levels etc are all within spec, so I assume the issue is noise on the line perhaps? Try checking with Area faults on 0800 561 0061 or if you have a VM landline 150 as small local faults are not listed on the VM status page.
One for a VM tech to sort out.
If you wait here a day or two a VM Mod will pick this up.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
04-02-2023 11:06 - edited 04-02-2023 11:07
You have an excessive amount of T3 timeouts and the BQM is pretty bad.
Your power levels etc are all within spec, so I assume the issue is noise on the line perhaps? Try checking with Area faults on 0800 561 0061 or if you have a VM landline 150 as small local faults are not listed on the VM status page.
One for a VM tech to sort out.
If you wait here a day or two a VM Mod will pick this up.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 06-02-2023 12:12
Hi amel2023,
Thanks for taking the time to contact us via the Community. It's lovely having you on board with us in the Forums. ⭐
We're sorry to hear you're having an issue with your connection. Taking a look at things this end I can see there has been a long term performance issue with the Hub.
We won't be able to fix this remotely so I would like to arrange for an engineer to come to take a look at this for you. I just need to confirm the address to ensure we are booking the visit on the correct account.
I have sent you a private message regarding this. Just click on the little plum envelope at the top right-hand side of the page to access your inbox.
Thanks,
on 06-02-2023 13:59
Hi amel2023,
Thanks for coming back to via private message to confirm your information.
I have booked you in for the next available appointment. To view this please sign in to My Virgin Media here: My VM. Once you log in scroll down to Orders & appointments then click on View your orders. Please note it can take up to 24 hours to show but you should also receive a text message with the details. You can also view this in the My VM app. If you have any issues with accessing your account or unable to see your visit, please do let us know and we’ll pop you a message to pass data protection and confirm the appointment details.
Just to confirm, 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 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.
We will continue to monitor your services and if we can see that the fault has cleared and the visit is no longer required we will cancel the appointment and let you know by text and email
Lets us know how the appointment goes.
Take care.
on 28-02-2023 08:42
Following the engineer coming out who couldn't find anything wrong other than a slightly loose coax connection I am still getting this issue. The timeouts are still increasing on the modem stats and I am still seeing packet loss on the connection monitoring. Can anyone advise how I can get this looked into further?
on 28-02-2023 08:43
Latest Hub Stats
Cable Modem StatusItem Status Comments
Acquired Downstream Channel(Hz) | 291000000 | Locked |
Ranged Upstream Channel(Hz) | 46200000 | Ranged |
Provisioning State | Online | Operational |
Downstream bonded channels
1 | 291000000 | -1.3 | 40 | QAM 256 | 20 |
2 | 163000000 | 0.2 | 41 | QAM 256 | 4 |
3 | 171000000 | 0.1 | 41 | QAM 256 | 5 |
4 | 179000000 | 0 | 41 | QAM 256 | 6 |
5 | 187000000 | 0 | 40 | QAM 256 | 7 |
6 | 195000000 | 0.2 | 41 | QAM 256 | 8 |
7 | 203000000 | 0.2 | 41 | QAM 256 | 9 |
8 | 211000000 | 0.3 | 41 | QAM 256 | 10 |
9 | 219000000 | 0.3 | 41 | QAM 256 | 11 |
10 | 227000000 | 0.2 | 41 | QAM 256 | 12 |
11 | 235000000 | 0 | 41 | QAM 256 | 13 |
12 | 243000000 | 0.3 | 41 | QAM 256 | 14 |
13 | 251000000 | 0.7 | 41 | QAM 256 | 15 |
14 | 259000000 | -1 | 41 | QAM 256 | 16 |
15 | 267000000 | -1.1 | 40 | QAM 256 | 17 |
16 | 275000000 | -1.3 | 40 | QAM 256 | 18 |
17 | 283000000 | -1.3 | 40 | QAM 256 | 19 |
18 | 299000000 | -1.4 | 40 | QAM 256 | 21 |
19 | 307000000 | -1.5 | 40 | QAM 256 | 22 |
20 | 315000000 | -1.5 | 40 | QAM 256 | 23 |
21 | 323000000 | -1.5 | 40 | QAM 256 | 24 |
22 | 331000000 | -1.6 | 40 | QAM 256 | 25 |
23 | 339000000 | -1.5 | 39 | QAM 256 | 26 |
24 | 347000000 | -1.6 | 40 | QAM 256 | 27 |
25 | 355000000 | -1.7 | 40 | QAM 256 | 28 |
26 | 363000000 | -1.5 | 40 | QAM 256 | 29 |
27 | 371000000 | -1.6 | 40 | QAM 256 | 30 |
28 | 379000000 | -1.6 | 40 | QAM 256 | 31 |
29 | 387000000 | -1.8 | 40 | QAM 256 | 32 |
30 | 395000000 | -1.9 | 40 | QAM 256 | 33 |
31 | 403000000 | -2 | 40 | QAM 256 | 34 |
Downstream bonded channels
1 | Locked | 40 | 0 | 0 |
2 | Locked | 41 | 23 | 0 |
3 | Locked | 41 | 1 | 0 |
4 | Locked | 41 | 1 | 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 | 1 | 0 |
12 | Locked | 41 | 0 | 0 |
13 | Locked | 41 | 0 | 0 |
14 | Locked | 41 | 0 | 0 |
15 | Locked | 40 | 0 | 0 |
16 | Locked | 40 | 1 | 0 |
17 | Locked | 40 | 0 | 0 |
18 | Locked | 40 | 0 | 0 |
19 | Locked | 40 | 1 | 0 |
20 | Locked | 40 | 1 | 0 |
21 | Locked | 40 | 1 | 0 |
22 | Locked | 40 | 0 | 0 |
23 | Locked | 39 | 0 | 0 |
24 | Locked | 40 | 1 | 0 |
25 | Locked | 40 | 2 | 0 |
26 | Locked | 40 | 2 | 0 |
27 | Locked | 40 | 5 | 0 |
28 | Locked | 40 | 0 | 0 |
29 | Locked | 40 | 2 | 0 |
30 | Locked | 40 | 3 | 0 |
31 | Locked | 40 | 3 | 0 |
Upstream bonded channels
0 | 46200000 | 37 | 5120 | QAM 64 | 3 |
1 | 39400000 | 36.5 | 5120 | QAM 64 | 4 |
2 | 32600000 | 36.5 | 5120 | QAM 64 | 5 |
3 | 23600000 | 36 | 5120 | QAM 64 | 6 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 13 | 0 |
1 | ATDMA | 0 | 0 | 3 | 0 |
2 | ATDMA | 0 | 0 | 4 | 0 |
3 | ATDMA | 0 | 0 | 148 | 1 |
General Configuration
Allowed |
3 |
Enabled |
3.1 |
wrkldJKDHSUBsgvca69834ncxv987 |
Primary Downstream Service Flow
1133 |
402500089 bps |
42600bytes |
0 bps |
29128 |
128000 bps |
4000bytes |
0 bps |
Primary Upstream Service Flow
234 |
38500089 bps |
42600bytes |
0 bps |
42600bytes |
Best Effort |
29125 |
128000 bps |
4000bytes |
0 bps |
1522bytes |
Best Effort |
Network Log
27-02-2023 18:40:06 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-02-2023 06:33:54 | warning | Dynamic Range Window violation |
27-02-2023 06:33:54 | warning | 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; |
27-02-2023 01:07:07 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-02-2023 21:14:49 | warning | 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; |
26-02-2023 21:14:49 | warning | Dynamic Range Window violation |
26-02-2023 15:02:08 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-02-2023 12:46:51 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-02-2023 11:43:03 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-02-2023 09:19:56 | warning | Dynamic Range Window violation |
26-02-2023 09:19:56 | warning | 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; |
24-02-2023 08:10:40 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
24-02-2023 01:14:58 | warning | Dynamic Range Window violation |
24-02-2023 01:14:58 | warning | 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; |
23-02-2023 17:54:40 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
23-02-2023 00:46:50 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 19:29:47 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 18:43:17 | 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.1; |
19-02-2023 14:11:40 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-02-2023 12:46:48 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-02-2023 01:02:29 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-02-2023 00:46:46 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
14-02-2023 01:01:44 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
13-02-2023 19:02:57 | warning | 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; |
13-02-2023 19:02:57 | warning | Dynamic Range Window violation |
13-02-2023 13:56:07 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-02-2023 21:07:42 | warning | Dynamic Range Window violation |
12-02-2023 21:07:42 | warning | 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; |
12-02-2023 19:11:14 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12-02-2023 12:46:44 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-02-2023 14:58:31 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-02-2023 08:48:59 | notice | CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 658121; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 02-03-2023 18:52
Hi @amel2023 thanks for your post here although we're sorry to hear of your concerns raised.
I'd like to look into this further for you, there appears to be an issue on the line so we may need a technician.
Please allow me to send you a PM so I can look into this further for you.
Kindly expect the PM from me to arrive shortly, and respond directly when you can!
Many thanks