Wednesday
Just noticed that most of the Downstream Channels have a high number of Pre RS Errors a few downstream channels also have high Post RS Errors.
The downstream corrected errors and the uncorrected errors are in the 100's of millions and increasing.
The Hub5 LOg shows frequent CMS Notices
CM-STATUS message sent. Event Type Code: - toggling between 24 and 16.
The Upstream Channels show zero errors
Modem was rebooted some 8hrs ago.
Hub 5 also refuses to go into Modem Mode !
Is the HUB 5 on the way out or is there an issue at the street cab ?
3.0 Downstream channels
1 | 586000000 | 1 | 34 | QAM 256 | 29 |
2 | 362000000 | 2.1 | 35 | QAM 256 | 1 |
3 | 370000000 | 2.2 | 37 | QAM 256 | 2 |
4 | 378000000 | 2.4 | 37 | QAM 256 | 3 |
5 | 386000000 | 2.2 | 36 | QAM 256 | 4 |
6 | 394000000 | 1.9 | 31 | QAM 256 | 5 |
7 | 402000000 | 1.9 | 35 | QAM 256 | 6 |
8 | 410000000 | 1.6 | 34 | QAM 256 | 7 |
9 | 418000000 | 1.4 | 31 | QAM 256 | 8 |
10 | 426000000 | 1.1 | 29 | QAM 256 | 9 |
11 | 434000000 | 0.9 | 31 | QAM 256 | 10 |
12 | 442000000 | 1.1 | 31 | QAM 256 | 11 |
13 | 450000000 | 1.3 | 33 | QAM 256 | 12 |
14 | 458000000 | 1.1 | 32 | QAM 256 | 13 |
15 | 466000000 | 1.5 | 32 | QAM 256 | 14 |
16 | 546000000 | 0.7 | 34 | QAM 256 | 24 |
17 | 554000000 | 0.8 | 32 | QAM 256 | 25 |
18 | 562000000 | 0.9 | 36 | QAM 256 | 26 |
19 | 570000000 | 0.7 | 36 | QAM 256 | 27 |
20 | 578000000 | 0.7 | 35 | QAM 256 | 28 |
21 | 602000000 | 0.9 | 32 | QAM 256 | 31 |
22 | 610000000 | 0.6 | 38 | QAM 256 | 32 |
23 | 618000000 | 0.1 | 38 | QAM 256 | 33 |
24 | 626000000 | 0.4 | 38 | QAM 256 | 34 |
25 | 634000000 | 0.4 | 34 | QAM 256 | 35 |
26 | 658000000 | 0.3 | 28 | QAM 256 | 36 |
27 | 666000000 | 0.2 | 34 | QAM 256 | 37 |
28 | 674000000 | 0.3 | 34 | QAM 256 | 38 |
29 | 682000000 | 0 | 30 | QAM 256 | 39 |
30 | 690000000 | 0.5 | 32 | QAM 256 | 40 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 34 | 339806 | 0 |
2 | Locked | 35 | 207 | 8 |
3 | Locked | 37 | 63 | 0 |
4 | Locked | 37 | 77 | 1 |
5 | Locked | 36 | 32 | 0 |
6 | Locked | 31 | 139444925 | 117662 |
7 | Locked | 35 | 448 | 2 |
8 | Locked | 34 | 7181 | 0 |
9 | Locked | 31 | 8815490 | 1 |
10 | Locked | 29 | 214082988 | 9 |
11 | Locked | 31 | 7541814 | 13479 |
12 | Locked | 31 | 186655325 | 18285537 |
13 | Locked | 33 | 5304476 | 0 |
14 | Locked | 32 | 2495161 | 0 |
15 | Locked | 32 | 838083 | 0 |
16 | Locked | 34 | 155318 | 0 |
17 | Locked | 32 | 1971676 | 0 |
18 | Locked | 36 | 73 | 0 |
19 | Locked | 36 | 142 | 0 |
20 | Locked | 35 | 1997 | 0 |
21 | Locked | 32 | 7251107 | 0 |
22 | Locked | 38 | 5 | 0 |
23 | Locked | 38 | 13 | 0 |
24 | Locked | 38 | 21 | 0 |
25 | Locked | 34 | 4267 | 0 |
26 | Locked | 28 | 706277852 | 104257 |
27 | Locked | 34 | 61264 | 0 |
28 | Locked | 34 | 344476 | 0 |
29 | Locked | 30 | 156361665 | 3566 |
30 | Locked | 32 | 41667493 | 383130 |
3.1 Downstream channels
41 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
41 | Locked | 34 | -1.6 | 196932617 | 192767441 |
Wednesday
The Post RS errors are a network issue that VM need to fix - it may be affecting more that just you.
Try both methods below to see if a fault is reported in your street :
Call 0800 561 0061 – this is an automated number.
https://www.virginmedia.com/help/check/status/identification/identify
When you say will not go into Modem mode, what happens ? ( a screen shot perhaps if there is an error message )
Wednesday
No Broadband errors reported via Virgin Status. - just something about Sky+ and football !!
Re Modem Mode . I tick the Modem Mode box, save and reboot.. Hub 5 returns in Router Mode (white light) and no reported error. I'll give it another go in the morning as hub as been rebooted several times since last trying.
Wednesday
Check that all coax connectors are properly fitted and there is no damage to the cables.
Thursday
OK, Once more I've tried setting modem mode. When hitting save , the spinning star appears, but the modem does
not reset or reboot and no changes are made. Is a hub pinhole reset now called for ?
Thursday
SNR far too low on a lot of channels. Because of the random spread of errors I don’t think it’s noise ingress, but more likely a faulty hub or just possibly a cable/street box problem, I would choose the former. It would also be nice to see the upstream figures, they are just as important.
Thursday
Thanks Tudor. I'll give the hub a pinhole reset tomorrow and see if that helps.
3.0 Upstream channels
0 | 49600000 | 50.3 | 5120 | QAM 64 | 5 |
1 | 43100000 | 48.8 | 5120 | QAM 64 | 6 |
2 | 36600000 | 45 | 5120 | QAM 64 | 7 |
3 | 30100000 | 47 | 5120 | QAM 64 | 8 |
4 | 23600000 | 49 | 5120 | QAM 64 | 10 |
3.0 Upstream 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 |
3.1 Upstream channels
13 | 10.4 | 43.5 | 2K | QAM 256 |
3.1 Upstream channels
13 | OFDMA | 208 | 74000000 | 0 |
Thursday
You have high power levels for upstream and low power levels for downstream. This is indicative of one of these, a long way from cabinet or bad cable to cabinet. The first could possible be helped by a move to a different tap on the street cabinet, the second a cable re pull possible with a higher grade coax. In either case you need a technicians visit to rectify. Call Customer Services on 0345 454 1111/150 if you have a VM landline or wait two or three days for a VM staff member to get to your post.
Thursday
Cable is from the Comtel days ! I'll call CS in the morning. Thank you.
Hub 5 just mysteriously reboot and came up in ROUTER mode !!
Still lots of PRE RS Errors, but less POST RS
The Corrected and uncorrected errors remain hi.
Network Log
31-10-2024 22:00:12 | notice | GUI Login Status - Login Success from LAN interface |
31-10-2024 21:53:04 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:52:42 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
31-10-2024 21:52:38 | 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; |
31-10-2024 21:52:37 | notice | US profile assignment change. US Chan ID: 13; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:52:37 | warning | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:52:32 | 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; |
31-10-2024 21:52:28 | notice | TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:52:26 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:52:23 | notice | Honoring MDD; IP provisioning mode = IPv4 |
31-10-2024 21:52: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; |
31-10-2024 21:52:13 | critical | Cable Modem Reboot because of - Reboot Timezone Change |
31-10-2024 21:49:46 | 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; |
31-10-2024 21:49:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:32 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:27 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:27 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:15 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:14 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:11 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:11 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:04 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:04 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:49:04 | 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; |
31-10-2024 21:49:04 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:48:59 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:48:59 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:48:53 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:48:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:48:51 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:48:51 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:48:50 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-10-2024 21:48:50 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thursday
Don’t like this message "Cable Modem Reboot because of - Reboot Timezone Change" tends to imply a hub fault, especially as it’s rebooted. Just have to see what the technician says.