cancel
Showing results for 
Search instead for 
Did you mean: 

Anyone know what these errors mean?

hughesie2006
Joining in

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;

 

1 ACCEPTED SOLUTION

Accepted Solutions

Andrew-G
Alessandro Volta

That's one nasty network log.  If you want to know what it means, look at the link below.

https://community.virginmedia.com/t5/Speed/Hub-status-data-understanding-network-log-messages/m-p/47...

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.

See where this Helpful Answer was posted

3 REPLIES 3

Andrew-G
Alessandro Volta

That's one nasty network log.  If you want to know what it means, look at the link below.

https://community.virginmedia.com/t5/Speed/Hub-status-data-understanding-network-log-messages/m-p/47...

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.

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!

Tipped over again today with the following entries in the network log...I HAVE NOT REBOOTED THE HUB YET

9/08/2021 14:43:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2021 14:42:34criticalReceived 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

13940003438.5512064 qam4
24620001738.5512064 qam3
35370002140512064 qam2
46029999340.8512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0010

 

DOWNSTREAM LOG

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

13310000001.740256 qam25
22670000001.538256 qam17
32750000001.440256 qam18
42830000001.740256 qam19
52910000001.740256 qam20
6299000000240256 qam21
73070000001.940256 qam22
83150000001.740256 qam23
9323000000240256 qam24
103390000001.540256 qam26
113470000001.240256 qam27
123550000000.540256 qam28
133630000000.740256 qam29
143710000000.740256 qam30
153790000000.540256 qam31
163870000000.540256 qam32
173950000000.240256 qam33
184030000000.240256 qam34
194110000000.240256 qam35
20419000000-0.240256 qam36
21427000000-0.240256 qam37
22435000000-0.540256 qam38
23443000000-0.540256 qam39
24451000000-0.538256 qam40



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked40.350
2Locked38.950
3Locked40.300
4Locked40.350
5Locked40.300
6Locked40.340
7Locked40.370
8Locked40.300
9Locked40.350
10Locked40.360
11Locked40.300
12Locked40.900
13Locked40.3120
14Locked40.990
15Locked40.300
16Locked40.3200
17Locked40.9140
18Locked40.3190
19Locked40.3200
20Locked40.900
21Locked40.300
22Locked40.300
23Locked40.340
24Locked38.900