Menu
Reply
  • 3
  • 0
  • 0
mbcmf
Joining in
100 Views
Message 1 of 6
Flag for a moderator

Super Hub 2 - Connection Dropping can s

For the past few months I have been having to reset the super hub2 more and more to get the wifi back up and working. Over the past week its been hell, almost un-usable and right now my 200Mb connection is performing at around 10% and is dropping wifi constantly. Pretty Sure i need an eng to come out can some one have a look at the info below and confirm i need physical support

Physical Hub has forward path attenuator 10db Attached, removing makes connection worse. logs and errors below are with attenuator attached

errors in log are 

01/01/2017 23:24:01 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC

There were also some T3 errors but currently not showing in log due to previous error filling entire log view in the same second

Hardware Version 3.11
Software Version V1.01.31

Downstream Acquisition Locked
Primary Frequency 299000000 Hz
DHCP Done
TFTP Done
Time Of Day 23:27:46 GMT
Security BPI+
Counters T1,T2,T3,T4,Sync,Resets 000,000,1042,000,000,000

Downstream

Lock Status Channel ID Frequency Modulation Rx Power RxMER Pre RS Errors Post RS Errors
Locked 13 299000000 Hz 256 QAM -2.9 dBmV 35.4 dB 463 315
Locked 9 267000000 Hz 256 QAM -3.2 dBmV 35.2 dB 615 301
Locked 10 275000000 Hz 256 QAM -3.2 dBmV 35.2 dB 523 311
Locked 11 283000000 Hz 256 QAM -3.0 dBmV 35.2 dB 1192 969
Locked 12 291000000 Hz 256 QAM -2.9 dBmV 35.4 dB 1053 931
Locked 14 307000000 Hz 256 QAM -3.2 dBmV 35.4 dB 455 307
Locked 15 315000000 Hz 256 QAM -3.1 dBmV 35.2 dB 1168 923
Locked 16 323000000 Hz 256 QAM -3.1 dBmV 35.2 dB 1204 979

Upstream

Lock Status Channel ID Frequency Modulation Tx Power Mode Channel Bandwidth Symbol Rate
Locked 2 31000000 Hz ATDMA 37.8 dBmV 16QAM 1600000 Hz 1280 Ksym/sec
NotLocked 0 0 Hz 0 dBmV 0 Ksym/sec
NotLocked 0 0 Hz 0 dBmV 0 Ksym/sec
Locked 1 37600000 Hz ATDMA 36.3 dBmV 16QAM 6400000 Hz 5120 Ksym/sec

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=2635ms TTL=55
Reply from 8.8.8.8: bytes=32 time=2129ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1879ms TTL=55
Reply from 8.8.8.8: bytes=32 time=1408ms TTL=55

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1408ms, Maximum = 2635ms, Average = 2012ms

speedtest.net ping 62ms download speed 7.67 upload speed 0.19 on the Vivid 200 Package

Thanks for any Help

 

 

 

 

 

 

0 Kudos
Reply
  • 3
  • 0
  • 0
mbcmf
Joining in
95 Views
Message 2 of 6
Flag for a moderator

Re: Super Hub 2 - Connection Dropping can s

Another super hub reboot has seen the device operating better again back up to 200Mb and 10Mb for right now but how long will it last, is the question any where from 5 minutes to a few hours by the last weeks performances

current log after reboot

Date Time Error Number Error Description
01/01/2017 23:45:47 GMT 66050310 Auth Success - Web login successful.
01/01/2017 23:45:47 GMT 66050310 Auth Success - Web login successful.
01/01/2017 23:44:49 GMT 68010302 DHCP WAN IP - 92.232.35.185
01/01/2017 23:43:43 GMT 68000407 TOD established
Time Not Established Time Not Established 84000510 Downstream Locked Successfully
01/01/2017 23:42:09 GMT 66050310 Auth Success - Web login successful.
01/01/2017 23:37:02 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:37:01 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:37:01 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:37:00 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:36:59 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:36:57 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:36:56 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:36:56 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:36:55 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:36:55 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:36:54 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:36:54 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:36:53 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:36:52 GMT 82000200 No Ranging Response received - T3 time-out

0 Kudos
Reply
  • 3
  • 0
  • 0
mbcmf
Joining in
92 Views
Message 3 of 6
Flag for a moderator

Re: Super Hub 2 - Connection Dropping can s

connection back to failing speedtest fails to complete error log below

 

Date Time Error Number Error Description
01/01/2017 23:52:39 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:39 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:38 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:38 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:37 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:37 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:36 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:36 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:35 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:35 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:34 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:34 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:33 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:33 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:32 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:32 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:31 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:31 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC
01/01/2017 23:52:30 GMT 82000200 No Ranging Response received - T3 time-out
01/01/2017 23:52:30 GMT 82000700 Unicast Ranging Received Abort Response - initializing MAC

0 Kudos
Reply
  • 8.99K
  • 756
  • 1.87K
Superuser
Superuser
51 Views
Message 4 of 6
Flag for a moderator

Re: Super Hub 2 - Connection Dropping can s

It looks like you have an upstream impairment on your local circuit with the high number of T3 errors you are polling.

Not sure why your connection is poorer without the 10dB FPA as your power levels would still be in spec.

It might be worth checking the coax cable from the hub to the cable entry point for obvious signs of damage and all connectors are hand tight.

I think you are correct about needing an engineer. You will need to contact VM to arrange this, 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.

  • 7.26K
  • 304
  • 519
Forum Team
Forum Team
34 Views
Message 5 of 6
Flag for a moderator

Re: Super Hub 2 - Connection Dropping can s

Hi mbcmf,

 

Welcome to the Community!

 

Really sorry to hear you're having trouble with your connection.

 

I'd like to check this out for you but I can't seem to locate your account. I've sent you a private message (purple envelope at the top right of your screen) so I can grab some details from you.

 

Speak soon! Smiley Very Happy

 

Josh


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply
  • 8.99K
  • 756
  • 1.87K
Superuser
Superuser
28 Views
Message 6 of 6
Flag for a moderator

Re: Super Hub 2 - Connection Dropping can s

Just noticed that the symbol rate has decreased to 1280KSymb/s on one of the downstreams which would confirm the upstream impediment.

0 Kudos
Reply