Menu
Reply
  • 4
  • 0
  • 0
hsar
Joining in
315 Views
Message 1 of 5
Flag for a moderator

Superhub constantly losing connection

Hi. My Hub 3.0 has been rebooting? (not sure) multiple times a day for the past two days. When it happens I also lose connection to the Hub as I'm unable to connect to or ping 192.168.0.1 which is why I think the superhub is the problem.

Some graphs:

No issues until 17/10/19 22:30

My Broadband Ping - VIVID 350

Yesterday

My Broadband Ping - VIVID 350

 

What I've tried and other info:

Made sure all connectors are tight

Factory reset the hub

Rebooted the hub

Same loss of connection wired

Strangely I was able to ping a printer on the same network over wifi but was unable to connect to or ping the hub when this last happened

Virgin Media website shows no issues and when I do run the test while I have no connection it comes back saying the equipment might be turned off

No problems with speed or packet loss when the connection is working

0 Kudos
Reply
  • 4
  • 0
  • 0
hsar
Joining in
313 Views
Message 2 of 5
Flag for a moderator

Re: Superhub constantly losing connection

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
178750000
Locked
Ranged Upstream Channel (Hz)
60300000
Locked
Provisioning State
Online
 

 

Downstream bonded channels

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

11787500000.938256 qam6
2186750000138256 qam7
3194750000138256 qam8
4202750000138256 qam9
52107500000.738256 qam10
62187500000.238256 qam11
7226750000038256 qam12
8234750000038256 qam13
9242750000-0.238256 qam14
10250750000038256 qam15
11258750000038256 qam16
12266750000038256 qam17
13274750000038256 qam18
14282750000-0.238256 qam19
15290750000-0.538256 qam20
16298750000-0.938256 qam21
17306750000-0.938256 qam22
18314750000-0.738256 qam23
19322750000-0.538256 qam24
20402750000-1.538256 qam25
21410750000-1.538256 qam26
22418750000-2.238256 qam27
23426750000-2.738256 qam28
24434750000-3.238256 qam29



Downstream bonded channels

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

1Locked38.9180
2Locked38.9180
3Locked38.9180
4Locked38.950
5Locked38.950
6Locked38.640
7Locked38.620
8Locked38.650
9Locked38.940
10Locked38.960
11Locked38.660
12Locked38.660
13Locked38.980
14Locked38.940
15Locked38.950
16Locked38.660
17Locked38.6200
18Locked38.660
19Locked38.660
20Locked38.600
21Locked38.650
22Locked38.660
23Locked38.620
24Locked38.62

0

 

 

Upstream bonded channels

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

1603000004.4512064 qam1
2537000004.5512064 qam2
3394000004.45512064 qam4
4462000004.475512064 qam3



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

 

0 Kudos
Reply
  • 4
  • 0
  • 0
hsar
Joining in
312 Views
Message 3 of 5
Flag for a moderator

Re: Superhub constantly losing connection

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-rtsxxl35016u-b.cm



Primary Downstream Service Flow

SFID7146
Max Traffic Rate402500089
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID7145
Max Traffic Rate38500089
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

 

 

Network Log

Time Priority Description

23/09/2019 05:28:48ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/09/2019 12:58:51ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/09/2019 04:26:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/09/2019 13:10:4ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/09/2019 17:58:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/09/2019 23:00:41ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/09/2019 08:51:22ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/09/2019 23:46:53criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2019 15:49:27ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2019 23:19:30ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 19:47:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 23:51:33criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 23:51:33Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 23:51:33criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 23:51:38Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2019 23:53:41criticalReceived 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;
01/01/1970 00:01:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2019 19:34:6ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/10/2019 03:04:9ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 2.11K
  • 120
  • 210
Forum Team
Forum Team
221 Views
Message 4 of 5
Flag for a moderator

Re: Superhub constantly losing connection

Hi Hsar,

 

Thank you for reaching out to us in our community, I am sorry to hear you have been losing connection.

 

I have checked your services and I cannot see any issues that could be causing this, how have your services been working since your last post on Saturday.

 

Kind regards

 

Paul.

0 Kudos
Reply
  • 4
  • 0
  • 0
hsar
Joining in
139 Views
Message 5 of 5
Flag for a moderator

Re: Superhub constantly losing connection

Seems fine now. Could it have been something on your end?

0 Kudos
Reply