Intermittent signal and High Errors

[Stuart1441]

I have, in the past had issues with interference on my line causing intermittent service for broadband. 

Today the signal is highly volatile and not sustainable for me to work from home, ive posted the router data below after 90 mins following a power cycle. if this is an incoming network issue could I request a service visit? 

Network Log
Time Priority Description
09-09-2024 10:16:51 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 21; 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;
09-09-2024 10:15:53 notice GUI Login Status - Login Success from LAN interface
09-09-2024 10:15:32 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:32 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:32 critical 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:32 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:32 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:32 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15: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-09-2024 10:15:31 critical 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:31 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:30 critical 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:30 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:30 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:30 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:15:30 critical 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:14:23 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:12:10 notice CM-STATUS message sent. Event Type Code: 20; 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;
09-09-2024 10:11:27 notice 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;
09-09-2024 10:10:55 notice REGISTRATION COMPLETE - Waiting for Operational status
09-09-2024 10:10:51 notice US profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:45 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;
09-09-2024 10:10:44 notice TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:41 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:39 notice Honoring MDD; IP provisioning mode = IPv4
09-09-2024 10:10:26 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;
09-09-2024 10:10:26 warning ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:22 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:22 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:16 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:16 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:11 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2024 10:10:11 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 338000000 4.2 40 QAM 256 26
2 138000000 6.3 40 QAM 256 1
3 146000000 6.2 40 QAM 256 2
4 154000000 6 39 QAM 256 3
5 162000000 6 40 QAM 256 4
6 170000000 5.9 40 QAM 256 5
7 178000000 5.6 40 QAM 256 6
8 186000000 5.5 40 QAM 256 7
9 194000000 5.3 40 QAM 256 8
10 202000000 4.9 40 QAM 256 9
11 210000000 4.8 40 QAM 256 10
12 226000000 4 40 QAM 256 12
13 234000000 3.9 40 QAM 256 13
14 242000000 3.7 40 QAM 256 14
15 250000000 3.4 40 QAM 256 15
16 258000000 3.3 40 QAM 256 16
17 266000000 3.2 40 QAM 256 17
18 274000000 3.2 40 QAM 256 18
19 282000000 3.9 40 QAM 256 19
20 290000000 4.2 40 QAM 256 20
21 298000000 4.1 40 QAM 256 21
22 306000000 4.4 40 QAM 256 22
23 314000000 4.4 40 QAM 256 23
24 322000000 4.2 40 QAM 256 24
25 330000000 4.1 40 QAM 256 25
26 346000000 4.1 40 QAM 256 27
27 354000000 4 40 QAM 256 28
28 362000000 3.8 40 QAM 256 29
29 370000000 3.5 40 QAM 256 30
30 378000000 3.3 40 QAM 256 31
31 386000000 3 40 QAM 256 32
3.0 Downstream channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40 408 797
2 Locked 40 1075 389
3 Locked 40 1603 1218
4 Locked 39 882 675
5 Locked 40 670 399
6 Locked 40 601 345
7 Locked 40 441 223
8 Locked 40 415 356
9 Locked 40 445 326
10 Locked 40 393 350
11 Locked 40 313 389
12 Locked 40 232 257
13 Locked 40 436 720
14 Locked 40 200 205
15 Locked 40 209 279
16 Locked 40 189 176
17 Locked 40 301 473
18 Locked 40 134 121
19 Locked 40 128 134
20 Locked 40 130 225
21 Locked 40 508 869
22 Locked 40 122 228
23 Locked 40 126 189
24 Locked 40 197 303
25 Locked 40 177 327
26 Locked 40 646 1115
27 Locked 40 373 749
28 Locked 40 152 224
29 Locked 40 176 337
30 Locked 40 186 305
31 Locked 40 148 255
3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33 94 4K 1840 QAM 4096 1108
3.1 Downstream channels
Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
33 Locked 39 -3.1 57061640 805

[jbrennand]

Check first for any “known network faults in your location - Look in 2 places

1) Try the “check service,”Area status webpage (https://www.virginmedia.com/help/service-status)

2) Then also Try the “free & automated” Service Status number - 0800 561 0061 - which usually gives the most up to date info. and tells you of more local issues and fix estimates, down to street cab/ postcode level.

Then reset the Hub again as below and post up a "full set" of data.

_______________

Switch the Hub off and unplug it from the mains supply for five minutes. Whilst it's off, do a quick check that all of your coax and ethernet cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Ensure there are no “unterminated cable loose ends. Disconnect all the connections and reconnect to be sure. Also check that the internal wiring is ok with no kinking or chaffing. When its light, check that all looks good with the outside cabling and wall box (no “staples, etc.,) piercing the cables. Then switch the Hub back on and leave ~5 minutes When all done, check back in the settings and ensure that the RS error counts and T3 errors have all reset to 0. Then check every hour or so to see if they start reappearing - they shouldn't. If they do (particularly the postRS and T3 ones) you have a problem (noise) that only a Tech visit will sort.
Also check the Upstream QAM’s are all at 64

But post up again,

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

Also, If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph”. Click the lower link (Share Live Graph) then, click generate. Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK
https://www.thinkbroadband.com/broadband/monitoring/quality

[Stuart1441]

Latest Data having followed the steps above; the connection over the last 24hrs has been unusable and worse than ever 

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 330000000 4.2 40 QAM 256 25
2 138000000 6.1 40 QAM 256 1
3 146000000 6 40 QAM 256 2
4 154000000 5.7 40 QAM 256 3
5 162000000 6 40 QAM 256 4
6 170000000 5.8 40 QAM 256 5
7 178000000 5.5 40 QAM 256 6
8 186000000 5.4 40 QAM 256 7
9 194000000 5.1 40 QAM 256 8
10 202000000 4.7 40 QAM 256 9
11 210000000 4.7 40 QAM 256 10
12 218000000 4.3 39 QAM 256 11
13 226000000 3.7 40 QAM 256 12
14 234000000 3.6 40 QAM 256 13
15 242000000 3.3 40 QAM 256 14
16 250000000 3 39 QAM 256 15
17 258000000 3.1 39 QAM 256 16
18 266000000 3 40 QAM 256 17
19 274000000 2.8 40 QAM 256 18
20 282000000 3.4 39 QAM 256 19
21 290000000 3.9 39 QAM 256 20
22 298000000 3.9 40 QAM 256 21
23 306000000 4.3 40 QAM 256 22
24 314000000 4.4 40 QAM 256 23
25 322000000 4.1 39 QAM 256 24
26 338000000 4.2 40 QAM 256 26
27 346000000 4 40 QAM 256 27
28 354000000 4.1 40 QAM 256 28
29 362000000 3.9 40 QAM 256 29
30 370000000 3.4 40 QAM 256 30
31 378000000 3.5 39 QAM 256 31
3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40 8849 12329
2 Locked 40 603802 77239
3 Locked 40 308291 84156
4 Locked 40 769018 80918
5 Locked 40 860239 174389
6 Locked 40 1554692 278553
7 Locked 40 1545842 416597
8 Locked 40 743404 109915
9 Locked 40 18268 12616
10 Locked 40 12206 11279
11 Locked 40 11058 9513
12 Locked 39 10196 8514
13 Locked 40 9192 7741
14 Locked 40 10051 7036
15 Locked 40 6004 6037
16 Locked 39 5656 5962
17 Locked 39 5750 5133
18 Locked 40 7071 7064
19 Locked 40 8193 6951
20 Locked 39 6640 7030
21 Locked 39 6531 7808
22 Locked 40 5464 5979
23 Locked 40 7646 7425
24 Locked 40 3998 4847
25 Locked 39 3545 5190
26 Locked 40 4032 5766
27 Locked 40 3966 5580
28 Locked 40 3187 4729
29 Locked 40 4413 7341
30 Locked 40 4260 5684
31 Locked 39 3453 5289
3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33 94 4K 1840 QAM 4096 1108
3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
33 Locked 39 -2.7 1813290287 10239

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 49600000 46.8 5120 QAM 64 1
1 43100000 46.3 5120 QAM 64 2
2 36600000 46.3 5120 QAM 64 3
3 30100000 46 5120 QAM 64 4
4 23600000 46 5120 QAM 64 9
3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0 ATDMA 0 264 0 0
1 ATDMA 0 264 0 0
2 ATDMA 0 264 0 0
3 ATDMA 0 264 0 0
4 ATDMA 0 264 0 0
3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
10 10.4 41.5 2K QAM 256
3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
10 OFDMA 208 74000000 0 0

Network Log

Time Priority Description
11-09-2024 06:58:23 notice 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;
11-09-2024 06:57:40 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 9 10 15 24 26 29 30; 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;
11-09-2024 06:57:35 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=
11-09-2024 06:57:23 warning MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:57:12 notice GUI Login Status - Login Success from LAN interface
11-09-2024 06:55:05 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 15 24 26 29 30; 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;
11-09-2024 06:54:58 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=
11-09-2024 06:54:43 warning MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:54:42 notice 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;
11-09-2024 06:48:21 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 15 24 26 29 30; 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;
11-09-2024 06:48:00 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=
11-09-2024 06:47:57 warning MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:43:28 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 6 7 8 9 10 11 12 13 14 15 16 17 19 20 21 22 23 24 26 27 28 29 30 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=
11-09-2024 06:43:21 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 15 24 26 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;
11-09-2024 06:43:11 warning MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:42:52 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:42:11 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 24 26 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;
11-09-2024 06:41:53 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 24 26 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;
11-09-2024 06:41:45 warning MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:41:45 notice CM-STATUS message sent. Event Type Code: 1; Chan ID: 24 26 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;
11-09-2024 06:41:40 notice 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;
11-09-2024 06:39:31 notice REGISTRATION COMPLETE - Waiting for Operational status
11-09-2024 06:39:27 notice US profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:39:21 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;
11-09-2024 06:39:20 notice TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:39:18 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:39:16 notice Honoring MDD; IP provisioning mode = IPv4
11-09-2024 06:39:04 warning ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:39:03 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;
11-09-2024 06:39:01 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:39:00 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;
11-09-2024 06:38:53 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 06:38:51 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;

[Stuart1441]

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 370000000 3.8 40 QAM 256 30
2 138000000 6.7 40 QAM 256 1
3 146000000 6.6 40 QAM 256 2
4 154000000 6.3 40 QAM 256 3
5 162000000 6.4 40 QAM 256 4
6 170000000 6.2 40 QAM 256 5
7 178000000 5.9 40 QAM 256 6
8 186000000 5.8 40 QAM 256 7
9 194000000 5.6 40 QAM 256 8
10 202000000 5.2 40 QAM 256 9
11 210000000 5.2 40 QAM 256 10
12 218000000 4.8 40 QAM 256 11
13 226000000 4.3 40 QAM 256 12
14 234000000 4.2 40 QAM 256 13
15 242000000 4 40 QAM 256 14
16 250000000 3.7 40 QAM 256 15
17 258000000 3.7 40 QAM 256 16
18 266000000 3.6 40 QAM 256 17
19 274000000 3.5 40 QAM 256 18
20 282000000 4.1 40 QAM 256 19
21 290000000 4.5 40 QAM 256 20
22 298000000 4.4 40 QAM 256 21
23 306000000 4.7 40 QAM 256 22
24 314000000 4.7 40 QAM 256 23
25 322000000 4.5 40 QAM 256 24
26 330000000 4.4 40 QAM 256 25
27 338000000 4.5 40 QAM 256 26
28 346000000 4.3 40 QAM 256 27
29 354000000 4.3 40 QAM 256 28
30 362000000 4.2 40 QAM 256 29
31 378000000 3.8 40 QAM 256 31
3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40 9693 13645
2 Locked 40 632744 95474
3 Locked 40 340299 98419
4 Locked 40 800682 101682
5 Locked 40 892268 187319
6 Locked 40 1681367 301678
7 Locked 40 1665197 436271
8 Locked 40 802254 115832
9 Locked 40 20911 14999
10 Locked 40 13730 12288
11 Locked 40 14860 13939
12 Locked 40 12824 12215
13 Locked 40 11437 10426
14 Locked 40 12919 10434
15 Locked 40 7076 7026
16 Locked 40 7110 7749
17 Locked 40 8546 9095
18 Locked 40 10179 10968
19 Locked 40 11442 11443
20 Locked 40 11814 14239
21 Locked 40 8955 11217
22 Locked 40 8436 9927
23 Locked 40 10360 11410
24 Locked 40 7044 9364
25 Locked 40 6171 8853
26 Locked 40 6793 9879
27 Locked 40 5218 7423
28 Locked 40 5300 7495
29 Locked 40 5644 8767
30 Locked 40 5769 7948
31 Locked 40 4627 6824
3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33 94 4K 1840 QAM 4096 1108
3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
33 Locked 39 -2.9 2191827964 13403

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 49600000 46.5 5120 QAM 64 1
1 43100000 46.3 5120 QAM 64 2
2 36600000 46.3 5120 QAM 64 3
3 30100000 46 5120 QAM 64 4
4 23600000 45.8 5120 QAM 64 9
3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0 ATDMA 0 273 72 0
1 ATDMA 0 273 72 0
2 ATDMA 0 273 72 0
3 ATDMA 0 273 72 0
4 ATDMA 0 273 72 0
3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
10 10.4 41.7 2K QAM 256
3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
10 OFDMA 208 74000000 17 0

Network Log

Time Priority Description
11-09-2024 17:18:22 notice GUI Login Status - Login Success from LAN interface
11-09-2024 17:17:00 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 17:14:37 notice 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;
11-09-2024 17:11:16 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 17:09:23 notice CM-STATUS message sent. Event Type Code: 16; 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;
11-09-2024 12:37:01 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:37:01 critical 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:36:37 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:36:32 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:36:18 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:36:18 critical 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:35:54 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:35:46 critical 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:35:46 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:35:14 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:35:14 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:35:14 critical 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:34:41 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:34:40 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:34:40 critical 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:33:36 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:33:36 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 5 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 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;
11-09-2024 12:33:24 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:33:21 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 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;
11-09-2024 12:33:13 warning MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 12:33:11 notice 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;
11-09-2024 10:33:34 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 5 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 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;
11-09-2024 10:33:34 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 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;
11-09-2024 10:33:28 warning MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 10:22:41 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 10:22:05 critical 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 10:22:05 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2024 10:21:41 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Client62]

No more stats ... please !

Check if there is a fault in your locality as requested in the post from jbrennand

[Martin_N]

Hi Stuart1441,

Thank you for your post. We're very sorry to hear about the issue with your broadband service. 

We are happy to take a look into this for you. 

I will private message you now to confirm your details. 

^Martin

[gmij1961]

 I have just had a similar issue with unexplained error rate ,especially pre & post rss errors  which I now fixed by doing something very simple and I am still a bit gobsmacked with what I  now think is a simple old school fix . How I got to there  was I had issues  with my internet failures which looked beyond a UBR level and more with the VM core network , whilst that specific issue went away a few weeks ago   I  had  then started  looking at my Hub 3.0  network logs , I kept on getting millions or prerss errors across random channels on a random sporadic basis  which was not healthy . Rebooting would reset but when you I wasn't looking the counts would rise astronomically on any channel with a random pattern

As a result of handling my previous internet issues and the way VM hadn't really done anything I raised a further  complaint to VM whose response was they would send a tech round to look at my issues which I agreed to. However I had a problem in the fact for the last 6 years my router had been sitting in my back room  and my installation was in the front of my house . Knowing that VM could rightly say my install was not in the right place I put my router back to where it should be , and the error count got  far worse   when common sense would say it should have got better. !!

The fundamental difference being in my cable route to the back of the house I have a splitter which has a 3db attenuation factor . So removing the attenuation made the problem worse the obvious answer was to add attenuation . So given that  I choose to add a 10db inline attenuator and have never seen such a monumental change . I rebooted  5 hours ago and since I there is  no prerss error count is above 12 ( average is 6)  on any channel  and there are simply Zero post errors . Before that even if I rebooted there would at least 100 prersserrors after reboot and then the count would just to millions randomly and intermittently on random channels , there was no consistency

Am admission I have is I spent the 17 years working for NTL / Virginmedia and my specialised area was the Liberate  TV platform and 20 years ago if you had a Liberate STB which would not lock on to the return path one of the 1st things anyone did was to add / remove an attenuator  and it would regularly work and quite frankly I am kicking myself to why I didn't try this earlier., but then  I have never had an issue with a broadband router that did not lock onto the return path unless there was fault

Perhaps a reason why is I have got older etc but also when I look back at all the threads I have seen in the last month there seems to be little reference to adding or a removing attenuation , which is easy to do and  can be so effective. I am not a Docis expert and perhaps it could be said that adding attenuation is masking another problem 

Compared to Broadband router Liberate STB's  were so much more sensitive , but perhaps having such a level of sensitivity meant the network was maintained to higher standard 

[gmij1961]

Something that interests me here is the presumption that issue lies with the CPE equipment and the Docsis part of the end to end network . I only noticed by errors were excessively high as I was trying to figure out an issue that was most likely beyond the  UBR . From experience when there are Docis issues my router will restart spontaneously with all the pain of waiting for 6 minute reboot .  When I had my issue a month ago I was quite clearly losing network packets to various end points . DNS is always going to be the first notable point of failure but on this occassion while I could still ping my DNS server it was unable to resolve . Unfortunately I only saw this once so I can't say in conclusive but there is strong indication that the issue lay beyond the UBR . The other significant clues was Router was not failing , and I still had a dial tone on the phone , however when I tried to dial there was no response again pointing to an issue beyond the UBR . My router only failed when I ran the "network diagnsotics" . Before if failed and needed rebooting it was correctly picking up on a Network issue but it was also complaining about local wireless issues . To me that shows the router was struggling and this is where I think the reduction of such errors will improve router performance especially in terms wifi . As a thin client that takes 6 minutes to reboot that suggest it is more than a bit busy . If you strip of all the applications then the basic OS should boot up in a fraction of that time .  However in terms Docis and maintaining its return path lock they are far more robust than earlier Docis STB's which would range for any number of reasons.

In the 1990's Sun used the slogan the "Network is the computer" which mean the Network is Internet device end points , Pc , Laptop etc at one end the the service provider at the other  and any element including the end points can generate what is perceived as a network issue .  I.E a customer device that running 100% CPU will not stream properly . The current fashion is to look at the network starts at the cable at the client end and stops with the network on the server or any sub section in between

There is very basic but useful network utility called PING and can narrow this kind of issues especially run to various end points and from a multiple  places with in the network path . When I worked for VM the public IP address of  any DOCIS was pingable with in the VM production network and in case like this that is far better starting point that sending a field tech to site

From my experience the errors that are being reported and are not healthy but if you are struggling with end to end connectivity as I think is the case  then issue lies else where  and the time it takes to get a Tech to site is potentially a waste of time if no one is qualifying that network connectivity in the background .  

VM like many deploy trunking technology where commonly  4 network pipes are combined into one . A problem with monitoring trunking is it most often done on the aggregate level and quite often is a single pipe fails or trunking simple isn't working it can be unseen unless you go down to device like . A not functioning pipe may show 25% utilization but in reality the working pipe is thrashing away at 100% and causing mayhem when that initial threshold is breached .  There are a whole host of loading  algorithms that can be deployed in trunking and is possible on lightly loaded trunk set-up only a handle of IP address sources will use a faulty link . It can be minefield at times which needs very close investigation at time and depending on load these issues can come go as the please