28-07-2021 05:53 - edited 28-07-2021 06:00
28/07/2021 04:22:35 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/07/2021 16:17:49 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/07/2021 05:41:47 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 16:36:39 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 10:41:8 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 02:51:34 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/07/2021 15:02:48 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/07/2021 15:02:48 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/07/2021 11:44:6 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 19:34:10 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 08:37:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 08:37:54 | Warning! | B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 08:36:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 08:35: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.0; |
19/07/2021 08:33:16 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 08:33:7 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 08:33:5 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 22:37:18 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 22:36:26 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 22:36:26 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 28-07-2021 05:51
on 28-07-2021 05:52
on 28-07-2021 06:01
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz) | 659000000 | Locked |
Ranged Upstream Channel (Hz) | 53700002 | Locked |
Provisioning State | Online |
on 28-07-2021 06:02
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 659000000 | 4.9 | 38 | 256 qam | 32 |
2 | 475000000 | 1.4 | 38 | 256 qam | 9 |
3 | 483000000 | 1.7 | 38 | 256 qam | 10 |
4 | 491000000 | 1.5 | 38 | 256 qam | 11 |
5 | 499000000 | 2 | 38 | 256 qam | 12 |
6 | 507000000 | 3 | 40 | 256 qam | 13 |
7 | 515000000 | 2.7 | 40 | 256 qam | 14 |
8 | 523000000 | 2.7 | 38 | 256 qam | 15 |
9 | 531000000 | 3.4 | 38 | 256 qam | 16 |
10 | 539000000 | 3.4 | 40 | 256 qam | 17 |
11 | 547000000 | 2.7 | 40 | 256 qam | 18 |
12 | 555000000 | 3.2 | 38 | 256 qam | 19 |
13 | 563000000 | 3.5 | 40 | 256 qam | 20 |
14 | 571000000 | 3.7 | 38 | 256 qam | 21 |
15 | 579000000 | 3.5 | 40 | 256 qam | 22 |
16 | 587000000 | 4.1 | 40 | 256 qam | 23 |
17 | 595000000 | 4.5 | 40 | 256 qam | 24 |
18 | 603000000 | 4.1 | 38 | 256 qam | 25 |
19 | 611000000 | 4.6 | 38 | 256 qam | 26 |
20 | 619000000 | 5.1 | 38 | 256 qam | 27 |
21 | 627000000 | 5 | 38 | 256 qam | 28 |
22 | 635000000 | 4.5 | 38 | 256 qam | 29 |
23 | 643000000 | 5 | 38 | 256 qam | 30 |
24 | 651000000 | 4.9 | 38 | 256 qam | 31 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 104 | 0 |
2 | Locked | 38.9 | 756 | 434 |
3 | Locked | 38.9 | 563 | 14 |
4 | Locked | 38.9 | 581 | 46 |
5 | Locked | 38.9 | 514 | 301 |
6 | Locked | 40.3 | 337 | 273 |
7 | Locked | 40.3 | 366 | 1 |
8 | Locked | 38.9 | 391 | 184 |
9 | Locked | 38.9 | 303 | 291 |
10 | Locked | 40.3 | 173 | 0 |
11 | Locked | 40.3 | 259 | 1 |
12 | Locked | 38.9 | 230 | 245 |
13 | Locked | 40.3 | 138 | 81 |
14 | Locked | 38.9 | 131 | 0 |
15 | Locked | 40.3 | 168 | 66 |
16 | Locked | 40.3 | 130 | 190 |
17 | Locked | 40.3 | 101 | 0 |
18 | Locked | 38.9 | 135 | 12 |
19 | Locked | 38.9 | 131 | 171 |
20 | Locked | 38.9 | 64 | 51 |
21 | Locked | 38.9 | 94 | 0 |
22 | Locked | 38.6 | 115 | 87 |
23 | Locked | 38.9 | 71 | 105 |
24 | Locked | 38.6 | 65 | 0 |
on 28-07-2021 06:02
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700002 | 48 | 5120 | 64 qam | 2 |
2 | 39400000 | 46 | 5120 | 64 qam | 4 |
3 | 46200000 | 46.5 | 5120 | 64 qam | 3 |
4 | 60300000 | 48 | 5120 | 64 qam | 1 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 28-07-2021 06:27
The ethernet recommendation is to check whether you see the same connectivity problems when using a wired connection - I.e to see if it’s a problem with the whole connection or whether it’s just WiFi being rubbish… if the wired connection is good and stable then you can expect a 3rd party router to improve the situation…
your logs don’t look too bad.. there are some post-rs errors on the downstream channels though - when was the modem last rebooted?
When you suffer these outages, what are the lights on the front of the hub doing?
you could give the WiFi extenders a go, but they aren’t a great solution.. no harm in trying them tho since you already own them.. you’re better off looking at wireless mesh systems - check out the tp-link deco range for example.. before you do that though, it is definitely worth confirming whether or not the connection is stable when using ethernet as if it’s not, spending money on a 3rd party router is not going to resolve the issue…
28-07-2021 07:58 - edited 28-07-2021 08:01
Hi thanks for the quick reply, when the wifi goes there are no changes to the main white light on the router. There doesn't seem to be an issue with the ethernet but I can't run a ethernet cable down into my my wife's cellar office....would using one of those TP-Link Deco's get around that as I notice they have lan ports.
I actually rebooted the router yesterday.
on 28-07-2021 08:43
@paladinb wrote:I can't run a ethernet cable down into my my wife's cellar office....would using one of those TP-Link Deco's get around that as I notice they have lan ports.
Yes. The deco units connect together wirelessly. You can then plug things (pc, printer, whatever else) into them via ethernet if you want to.
The post-rs errors are higher than they should be.. ideally they should be at (or close to) 0. Keep an eye on how quickly they increment - there may be some noise ingress on your connection somewhere.
That said, if everything "feels" OK on ethernet then a 3rd party router/mesh system will result in a vast improvement of wireless connectivity in the house..
on 28-07-2021 08:49
Well my xbox and smart tv (for amazon prime,netflix and now tv) are hooked up via the ethernet and I've had no problems with the streaming so is that a good indication that the ethernet is stable for the most part.
"The post-rs errors are higher than they should be.. ideally they should be at (or close to) 0. Keep an eye on how quickly they increment - there may be some noise ingress on your connection somewhere." If that is the case what are my options?