Menu
Reply
IKbrunel
  • 185
  • 1
  • 29
Superfast
232 Views
Message 1 of 5
Flag for a moderator

HUB 3 NETWORK LOG CONTINUAL ERROR SHOWS

Continually seeing this in the log. Broadband is running normal. Upstream and downstream figures are all well within their normal parameters. Speed is correct M100.

HUB 3  Has been rebooted, several times.

 

Network Log

Time Priority Description

08/09/2020 08:26:34criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:26:34criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:25:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:25:14criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:22:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:22:14criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:19:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:19:34criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:18:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:18:15criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:16:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:16:55criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:14:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:14:15criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:12:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:12:55criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:11:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 08:11:35criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 00:09:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2020 00:09:49criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
VM-Jon
  • 884
  • 140
  • 172
Forum Team
Forum Team
226 Views
Message 2 of 5
Flag for a moderator

Re: HUB 3 NETWORK LOG CONTINUAL ERROR SHOWS

Good morning,

Thank you for your post, if that’s the errors you are seeing following a reboot then that’s perfectly normal.

All modem logs show errors, I really wouldn’t let it worry you especially when you say your service is running normally.

thank you

Jon


Here to help! I'm an install manager helping out whilst working from home. Find out more


0 Kudos
Reply
IKbrunel
  • 185
  • 1
  • 29
Superfast
220 Views
Message 3 of 5
Flag for a moderator

Re: HUB 3 NETWORK LOG CONTINUAL ERROR SHOWS

Thanks for your reply, this has only just started, is there a reason for it?

0 Kudos
Reply
VM-Jon
  • 884
  • 140
  • 172
Forum Team
Forum Team
213 Views
Message 4 of 5
Flag for a moderator
Helpful Answer

Re: HUB 3 NETWORK LOG CONTINUAL ERROR SHOWS

After a reboot it’s always there, you just may not have noticed it before.

Our head end is constantly communicating with the hub having it adjust it's transmit levels and frequencies. When the modem first starts it's registration it scans the downstream to find the correct channel then increasing it's power level until the cmts replies to increase or lower it's transmit level to hit the receiver at the correct power. The increasing or decreasing it's power level until it hits the receiver at the correct level is ranging. 
As it’s adjusting power and error is logged if there is no response.

Think of it like two people shouting to each other over a large field. One person shouts a message until the other person says okay I’ve got that. At first the person shouting the message may not be heard and need to keep turning up the volume until he has been heard. Every time the volume is increased an error is logged.

 


Here to help! I'm an install manager helping out whilst working from home. Find out more


0 Kudos
Reply
IKbrunel
  • 185
  • 1
  • 29
Superfast
198 Views
Message 5 of 5
Flag for a moderator

Re: HUB 3 NETWORK LOG CONTINUAL ERROR SHOWS

Now appears to be all back to normal. 

0 Kudos
Reply