Menu
Reply
boomkings
  • 1
  • 0
  • 0
Joining in
1,408 Views
Message 1 of 3
Flag for a moderator

Interpret the logs

Can someone help interpret the logs i found in the console.

 

 Wifi internet has been intermittently  on and off trying to figure out whats going on

17-06-2020 17:54:07warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:20noticeCable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17-06-2020 17:20:35warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:20noticeCable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17-06-2020 15:23:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17-06-2020 09:40:55warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:20noticeCable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17-06-2020 07:42:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16-06-2020 12:03:55warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:20noticeCable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16-06-2020 12:00:45warningMIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16-06-2020 11:58:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16-06-2020 11:58:44criticalReceived 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;
16-06-2020 11:57:44criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16-06-2020 11:57:44criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16-06-2020 11:57:43criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16-06-2020 11:57:43criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16-06-2020 11:57:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Tags (1)
0 Kudos
Reply
Tudor
  • 8.14K
  • 650
  • 1.42K
Alessandro Volta
1,387 Views
Message 2 of 3
Flag for a moderator

Re: Interpret the logs

Unless you are having problems, on their own, the messages nod not necessarily mean much. If you have a problem, please explain it. 


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
0 Kudos
Reply
Andrew-G
  • 6.18K
  • 1.08K
  • 2.62K
Very Insightful Person
Very Insightful Person
1,347 Views
Message 3 of 3
Flag for a moderator
Helpful Answer

Re: Interpret the logs

There's always a very few incidental T3 timeouts in a DOCSIS hub's log, but they shouldn't be cropping up with the frequency yours shows (not to mention T4 errors, and Ranging Retries Exhausted which is a variant on a T3 timeout).  So that log looks pretty grim, and the category and frequency of critical errors suggests noise on the upstream, which in turn is often associated with interrupted connections, high latency and poor downstream speeds. 

It could be a noise fault with the gear in the local cabinet or upstream of that, in which case it will affect multiple customers, but should be fixed quickly without you needing a technician.  Or it may be your cable connection is noisy or isn't properly setup, in which case you'll need a visit from a technician.  Forum staff can advise when they pick this post up.

You might want to do a series of speed tests, or set up a Broadband Quality Monitor at Thinkbroadband, and see what that indicates, because even though your log is black and white proof of a connection problem that has been generated by VM's own equipment, the company is not always very good at reading and reacting to that evidence.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks