on 18-08-2021 14:11
Every time my internet drops out (at least once per day) I see messages in the log that look like these….no expert but it looks like the sync between somewhere central and my router is being lost
I use this line for the days I work from home but this dropping out causes total havoc with my company VPN software.
Any thoughts on how to resolve or is this a technician call?
Thanks in advance for any help/advice given!
Time | Priority | Description |
18/08/2021 13:40:20 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:40:19 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:40:19 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:29:28 | 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; |
18/08/2021 13:29:16 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:29:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:29:11 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:29:11 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:29:1 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:26:48 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:26:44 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:26:44 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:26:44 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:14:25 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:14:16 | 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; |
18/08/2021 13:13:58 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:13:54 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:13:53 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:13:53 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/08/2021 13:12:16 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Answered! Go to Answer
on 18-08-2021 15:33
That's one nasty network log. If you want to know what it means, look at the link below.
In terms of what can you do about it, well you can phone VM's telephone support line if you're either naturally lucky, or have masochistic tendencies. Alternatively:
1) Check the coax connections are done up properly - finger tight
2) Restart the hub if you haven't already (most people have already done this by the time they post here)
3) Try a pinhole reset (wipes all settings and custom passwords)
4) Connect to the hub by clicking on this link http://192.168.0.1/ That should pull up the log in page for the hub. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots. Post that, do the same for the Upstream and Network log in subsequent replies. You'll get an error message when you post the Network log, just click on "post" a second time. Then we can check for any obvious problems with power, noise or error counts, but do this only when the hub has been running for 12-24 hours since the last restart, because when restarted all error counters are reset to zero.
on 18-08-2021 15:33
That's one nasty network log. If you want to know what it means, look at the link below.
In terms of what can you do about it, well you can phone VM's telephone support line if you're either naturally lucky, or have masochistic tendencies. Alternatively:
1) Check the coax connections are done up properly - finger tight
2) Restart the hub if you haven't already (most people have already done this by the time they post here)
3) Try a pinhole reset (wipes all settings and custom passwords)
4) Connect to the hub by clicking on this link http://192.168.0.1/ That should pull up the log in page for the hub. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots. Post that, do the same for the Upstream and Network log in subsequent replies. You'll get an error message when you post the Network log, just click on "post" a second time. Then we can check for any obvious problems with power, noise or error counts, but do this only when the hub has been running for 12-24 hours since the last restart, because when restarted all error counters are reset to zero.
on 18-08-2021 19:09
Andrew many thanks for all of that…interesting reading your post that you like linked.
I did a reboot today so will wait until it toppled over tomorrow (as it will) and then post the error log and the upstream / downstream logs so it has the 12-24 hrs as you suggest!
Appreciate your help, thank you!
on 19-08-2021 15:53
Tipped over again today with the following entries in the network log...I HAVE NOT REBOOTED THE HUB YET
9/08/2021 14:43:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/08/2021 14:42:34 | 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; |
UPSTREAM LOG
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400034 | 38.5 | 5120 | 64 qam | 4 |
2 | 46200017 | 38.5 | 5120 | 64 qam | 3 |
3 | 53700021 | 40 | 5120 | 64 qam | 2 |
4 | 60299993 | 40.8 | 5120 | 64 qam | 1 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
DOWNSTREAM LOG
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 1.7 | 40 | 256 qam | 25 |
2 | 267000000 | 1.5 | 38 | 256 qam | 17 |
3 | 275000000 | 1.4 | 40 | 256 qam | 18 |
4 | 283000000 | 1.7 | 40 | 256 qam | 19 |
5 | 291000000 | 1.7 | 40 | 256 qam | 20 |
6 | 299000000 | 2 | 40 | 256 qam | 21 |
7 | 307000000 | 1.9 | 40 | 256 qam | 22 |
8 | 315000000 | 1.7 | 40 | 256 qam | 23 |
9 | 323000000 | 2 | 40 | 256 qam | 24 |
10 | 339000000 | 1.5 | 40 | 256 qam | 26 |
11 | 347000000 | 1.2 | 40 | 256 qam | 27 |
12 | 355000000 | 0.5 | 40 | 256 qam | 28 |
13 | 363000000 | 0.7 | 40 | 256 qam | 29 |
14 | 371000000 | 0.7 | 40 | 256 qam | 30 |
15 | 379000000 | 0.5 | 40 | 256 qam | 31 |
16 | 387000000 | 0.5 | 40 | 256 qam | 32 |
17 | 395000000 | 0.2 | 40 | 256 qam | 33 |
18 | 403000000 | 0.2 | 40 | 256 qam | 34 |
19 | 411000000 | 0.2 | 40 | 256 qam | 35 |
20 | 419000000 | -0.2 | 40 | 256 qam | 36 |
21 | 427000000 | -0.2 | 40 | 256 qam | 37 |
22 | 435000000 | -0.5 | 40 | 256 qam | 38 |
23 | 443000000 | -0.5 | 40 | 256 qam | 39 |
24 | 451000000 | -0.5 | 38 | 256 qam | 40 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 5 | 0 |
2 | Locked | 38.9 | 5 | 0 |
3 | Locked | 40.3 | 0 | 0 |
4 | Locked | 40.3 | 5 | 0 |
5 | Locked | 40.3 | 0 | 0 |
6 | Locked | 40.3 | 4 | 0 |
7 | Locked | 40.3 | 7 | 0 |
8 | Locked | 40.3 | 0 | 0 |
9 | Locked | 40.3 | 5 | 0 |
10 | Locked | 40.3 | 6 | 0 |
11 | Locked | 40.3 | 0 | 0 |
12 | Locked | 40.9 | 0 | 0 |
13 | Locked | 40.3 | 12 | 0 |
14 | Locked | 40.9 | 9 | 0 |
15 | Locked | 40.3 | 0 | 0 |
16 | Locked | 40.3 | 20 | 0 |
17 | Locked | 40.9 | 14 | 0 |
18 | Locked | 40.3 | 19 | 0 |
19 | Locked | 40.3 | 20 | 0 |
20 | Locked | 40.9 | 0 | 0 |
21 | Locked | 40.3 | 0 | 0 |
22 | Locked | 40.3 | 0 | 0 |
23 | Locked | 40.3 | 4 | 0 |
24 | Locked | 38.9 | 0 | 0 |