Menu
Reply
Highlighted
  • 29
  • 0
  • 2
henry-root
On our wavelength
1,648 Views
Message 1 of 10
Flag for a moderator

Firmware version SuperHub 3

Getting intermittent outages on my Superhub3 which I only recently upgraded to. Has anyone confirmation of most up to date firmware pls? Mine in 9.1.116.608 Hardware ver 10. ThanksCat Very Happy

0 Kudos
Reply
  • 19.74K
  • 2.02K
  • 3.77K
Superuser
Superuser
1,639 Views
Message 2 of 10
Flag for a moderator

Re: Firmware version SuperHub 3

That is the most recent firmware
**********************************
I work for Virgin Media - but all opinions posted here are my own
  • 6.03K
  • 464
  • 1.01K
Tudor
Hero
1,635 Views
Message 3 of 10
Flag for a moderator
Helpful Answer

Re: Firmware version SuperHub 3

Go into your hub on 192.168.0.1 and post your up/down stream stats and network log. We will take a look at your circuit quality. 


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
  • 29
  • 0
  • 2
henry-root
On our wavelength
1,629 Views
Message 4 of 10
Flag for a moderator

Re: Firmware version SuperHub 3

Hi Tudor

Thanks. I've been having 3 or 4 intermittent outages daily ever since the router was installed on 24th Sept. White light go's off and solid red link light go's on. Normally I get excellent down and up speeds - 350/20 plus.

Network Log

Time Priority Description

2018-10-02 08:40:01.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 08:42:25.00criticalReceived 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;
1970-01-01 00:01:39.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:35:33.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:35:41.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:35:41.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:35:49.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:35:49.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:35:50.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:35:53.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:37:18.00criticalReceived 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;
2018-10-02 11:37:54.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:38:32.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:41:08.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:41:08.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:41:08.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:41:09.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:41:15.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 11:44:07.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-10-02 13:18:10.00Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 29
  • 0
  • 2
henry-root
On our wavelength
1,627 Views
Message 5 of 10
Flag for a moderator

Re: Firmware version SuperHub 3

Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
12987500003.440256 qam21
2426750000240256 qam28
34187500002.240256 qam27
44107500002.540256 qam26
54027500002.540256 qam25
63227500003.740256 qam24
73147500003.740256 qam23
83067500003.540256 qam22
92907500003.540256 qam20
102827500003.740256 qam19
112747500003.940256 qam18
12266750000440256 qam17
132587500003.940256 qam16
142507500003.538256 qam15
152427500003.538256 qam14
162347500003.540256 qam13
172267500003.540256 qam12
182187500003.438256 qam11
19202750000438256 qam9
201947500004.840256 qam8
21186750000540256 qam7
221787500005.138256 qam6
23170750000538256 qam5
242107500003.238256 qam10


Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked40.360
2Locked40.9150
3Locked40.980
4Locked40.3200
5Locked40.3190
6Locked40.360
7Locked40.370
8Locked40.390
9Locked40.9130
10Locked40.950
11Locked40.350
12Locked40.380
13Locked40.3110
14Locked38.9110
15Locked38.960
16Locked40.370
17Locked40.390
18Locked38.9110
19Locked38.960
20Locked40.3100
21Locked40.360
22Locked38.990
23Locked38.9280
24Locked38.960
0 Kudos
Reply
  • 29
  • 0
  • 2
henry-root
On our wavelength
1,626 Views
Message 6 of 10
Flag for a moderator

Re: Firmware version SuperHub 3

Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
13940000038.8512032 qam2
22580000038.8512016 qam4
33260000038.8512016 qam3
44620000038.8512032 qam1


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
  • 29
  • 0
  • 2
henry-root
On our wavelength
1,620 Views
Message 7 of 10
Flag for a moderator

Re: Firmware version SuperHub 3

The router lists faults but I also suspect the cabling. It was installed over 10 years ago.
0 Kudos
Reply
  • 29
  • 0
  • 2
henry-root
On our wavelength
1,607 Views
Message 8 of 10
Flag for a moderator

Re: Firmware version SuperHub 3

Any idea Tudor please?

 

OK so now the Virgin engineer has been I can see why you wanted these figures and maybe why you've not responded as they are all within parameter, except for the faults logged on status which the engineer could not explain.

0 Kudos
Reply
  • 6.03K
  • 464
  • 1.01K
Tudor
Hero
1,581 Views
Message 9 of 10
Flag for a moderator

Re: Firmware version SuperHub 3

Most, but not all, records in the log happened over a short period so I would expect some sort of “glitch” at that time. Yes, all your stats are ok, the only puzzling think is 2 channels on 16 and 2 channels on 32 QAM when I would expect all to be on 64 QAM. Only thing you could do is power cycle your hub and monitor the stats on a daily basis. 


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
  • 2.24K
  • 140
  • 566
cje85
Problem sorter
1,563 Views
Message 10 of 10
Flag for a moderator

Re: Firmware version SuperHub 3

16QAM is normal for the lower frequency channels in some areas.

The higher ones could be 64QAM in ideal conditions but 32QAM isn't necessarily a fault or cause for concern. 

0 Kudos
Reply