Menu
Reply
  • 1
  • 0
  • 0
JeanC123
Joining in
218 Views
Message 1 of 3
Flag for a moderator

Hub 3.0 Disconnecting

I have been having issues for the last 3 days where the router will appear to restart randomly. It has restarted itself 3 times in the last few hours and is very annoying. Can anyone help?

Downstream bonded channels

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

1243000000-3.538256 qam10
2171000000-1.738256 qam1
3179000000-1.938256 qam2
4187000000-1.938256 qam3
5195000000-2.238256 qam4
6203000000-2.238256 qam5
7211000000-2.738256 qam6
8219000000-2.738256 qam7
9227000000-2.938256 qam8
10235000000-3.238256 qam9
11251000000-3.538256 qam11
12259000000-3.538256 qam12
13267000000-438256 qam13
14275000000-438256 qam14
15283000000-4.238256 qam15
16291000000-438256 qam16
17299000000-4.238256 qam17
18307000000-438256 qam18
19315000000-4.438256 qam19
20323000000-4.438256 qam20

 

Upstream bonded channels

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

1462000025.05512064 qam1
2257999934.9512064 qam4
3325999985.05512064 qam3
4393999885.05512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Network Log

Time Priority Description

03/08/2019 05:27:29criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:30criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:31criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:32criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:33criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:33criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:34criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:34criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:35criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:36criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:37criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:27:37criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:28:26criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/08/2019 05:28:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 11.8K
  • 1.08K
  • 2.56K
griffin
Alessandro Volta
197 Views
Message 2 of 3
Flag for a moderator

Re: Hub 3.0 Disconnecting

The logs are showing the Hub dropping connection and restarting.
The Upstream is also running hot.

You will need to contact VM for resolution, either by waiting here about a week until a VM Forum Team Member picks up the thread, or give them a call on 150 from a VM line or 0345 454 1111 for a quicker response.

 

0 Kudos
Reply
  • 1.15K
  • 66
  • 210
Forum Team
Forum Team
161 Views
Message 3 of 3
Flag for a moderator

Re: Hub 3.0 Disconnecting

Hi JeanC123,

 

Welcome to our forums and thank you for your post. I'm sorry that you've been having intermittent broadband issues.

 

In taking a look at the backend of your services, it appears that there has been a network fault in your area which would account for these symptoms. Everything looks within spec again now, how's everything been since your post?

 

Thanks,

Rachael

0 Kudos
Reply