Menu
Reply
Jamie-owens
  • 7
  • 0
  • 0
Tuning in
141 Views
Message 1 of 4
Flag for a moderator

Critical Errors

Hello,

I have noticed in my router error log, many critical errors. I sometimes notice also that my connection cuts out for a few minutes. Is there something wrong?

 

Network Log

Time Priority Description

05/02/2021 19:31:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2021 02:29:39Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2021 02:29:13Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2021 02:29:13criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2021 02:29:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2021 02:27:18Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/02/2021 15:23:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2021 13:43:31Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2021 10:01:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2021 04:51:52noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2021 04:51:52ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/01/2021 00:30:16criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/01/2021 16:51:52noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/01/2021 16:51:52ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2021 10:53:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2021 04:51:53noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2021 04:51:53ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/01/2021 06:16:1criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 16:51:52noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 16:51:52ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Downstream bonded channels

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

14110000004.938256 qam31
22030000004.338256 qam9
32110000004.338256 qam10
42190000003.938256 qam11
52270000003.237256 qam12
62350000002.237256 qam13
72430000002.738256 qam14
82510000003.238256 qam15
9259000000438256 qam16
102670000004.338256 qam17
112750000004.338256 qam18
122830000004.538256 qam19
132910000004.538256 qam20
14299000000538256 qam21
153070000005.538256 qam22
163150000005.338256 qam23
17323000000538256 qam24
18363000000438256 qam25
193710000004.538256 qam26
203790000005.338256 qam27
213870000005.538256 qam28
223950000005.638256 qam29
23403000000538256 qam30
244190000004.538256 qam32



Downstream bonded channels

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

1Locked38.9819678
2Locked38.93414679
3Locked38.619771118
4Locked38.621361194
5Locked37.630401142
6Locked37.67296846
7Locked38.98289342
8Locked38.62913247
9Locked38.6946283
10Locked38.6869302
11Locked38.9768315
12Locked38.6784373
13Locked38.9649513
14Locked38.61285677
15Locked38.91086632
16Locked38.61385756
17Locked38.61900748
18Locked38.9992266
19Locked38.9927416
20Locked38.9879637
21Locked38.9546812
22Locked38.9794887
23Locked38.6867955
24Locked38.61031368

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

16029997445.5512064 qam1
23940000044512064 qam4
34620001944512064 qam3
45369999845.5512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0080
2ATDMA0090
3ATDMA0090
4ATDMA0080

 

0 Kudos
Reply
jbrennand
  • 20.58K
  • 2.19K
  • 3.63K
Very Insightful Person
Very Insightful Person
127 Views
Message 2 of 4
Flag for a moderator

Re: Critical Errors

First switch the Hub off for 5 minutes AND unplug it from the mains. Whilst it's off, do a quick check that all of your coax 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, check that all looks good with the outside cabling and wall box. Then switch it on again and leave 5 minutes

Then Do a Hub “pinhole reset” - make sure the 2 passwords on the Hub sticker are still there and legible first ! Disconnect any ethernet cables from the Hub, and then with the Hub still "switched on" throughout, press pin in firmly with paper clip/SIM tray tool or similar "thin thing" and hold it firmly for at least 60 seconds, release the pin, leave for 10’ to stabilise - dont manually switch it off at any time.

When done, check back in the settings and ensure that the RS error counts have all reset to 0. Then check every hour or two for the next day or two to see if they start reappearing - they shouldn't. If they do (particularly the postRS ones) you have a problem (noise) that only a Tech visit will sort.


Finally if you haven’t already, set up a free and secure “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” (as per instructions on the TB website) when it starts to develop.

https://www.thinkbroadband.com/broadband/monitoring/quality

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router +2 Airport Express's. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
Jamie-owens
  • 7
  • 0
  • 0
Tuning in
60 Views
Message 3 of 4
Flag for a moderator

Re: Critical Errors

Thanks for your response. I did everything you advised but I am still getting the following error;

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Here is a link to my BQM. It was down for half hour or so today while I unplugged the router to check cables and reset it back to its factory settings.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/6441b06329b2eb315db1cda760caaa698bfbee9f
0 Kudos
Reply
Jamie-owens
  • 7
  • 0
  • 0
Tuning in
20 Views
Message 4 of 4
Flag for a moderator

Re: Critical Errors

Can anyone help please?

0 Kudos
Reply