Hub3 with old firmware

[Tomo72]

Hi all,

I recently reinstalled the Hub3 I was sent a number of years ago and upped my package to M350. All seems to be working ok but the Hub3 has very old firmware 9.1.116V. I understand this should update automatically but it hasn't done so yet. Can this be forced by VM?

[lotharmat]

I'd take the view: If it ain't broke - Don't try and fix it!. Firmware can be so buggy and not rolled back!

If you get issues - look to chase up the upgrade but if no issues - Keep quiet! 😉

[Tomo72]

The only problem is this;

[lotharmat]

Oh... That's a problem but could most likely caused by a dodgy connection.

Can you post your Hub status and logs?
Someone should be spot if there is a problem
Navigate to http://192.168.0.1 (or http://192.168.100.1 - if in modem mode)
Don't log in!
Click on 'router status'
Copy/paste the data from each of the tabs as text into a 'REPLY' as opposed to 'QUICK REPLY'. The forum software will remove the MAC addresses for you (you will likely need to click the 'post' button again).

[Tomo72]

Downstream bonded channels
Channel Frequency(Hz) Power
(dBmV) SNR
(dB) Modulation Channel ID
1 299000000 4.1 38.9 256 qam 21
2 451000000 3 38.9 256 qam 40
3 443000000 3.4 40.3 256 qam 39
4 435000000 3.2 38.9 256 qam 38
5 427000000 3 40.3 256 qam 37
6 419000000 3 38.9 256 qam 36
7 411000000 3.5 38.6 256 qam 35
8 403000000 3.7 38.9 256 qam 34
9 395000000 4 38.6 256 qam 33
10 387000000 4 38.9 256 qam 32
11 379000000 4 38.9 256 qam 31
12 371000000 4.1 38.9 256 qam 30
13 363000000 4.5 38.9 256 qam 29
14 355000000 4.8 38.9 256 qam 28
15 347000000 4.5 40.9 256 qam 27
16 339000000 4.6 38.9 256 qam 26
17 331000000 4.5 38.9 256 qam 25
18 323000000 4.9 40.3 256 qam 24
19 315000000 4.8 38.9 256 qam 23
20 307000000 4.8 38.9 256 qam 22
21 291000000 3.9 38.9 256 qam 20
22 283000000 3.5 38.9 256 qam 19
23 275000000 3.5 38.9 256 qam 18
24 267000000 3.2 38.9 256 qam 17

[Tomo72]

Upstream bonded channels
Channel ID Frequency(Hz) Mode Power
(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)
11 32600000 ATDMA 40.8 64 qam 6400000 5120
7 46200000 ATDMA 40.8 64 qam 6400000 5120
12 25800000 ATDMA 40.8 64 qam 6400000 5120
8 39400000 ATDMA 40.8 64 qam 6400000 5120

[Tomo72]

General Configuration Value
Network access
Enabled
Maximum Number of CPEs
1
Baseline Privacy
Enabled
Docsis Mode
Docsis30
Config file
cmreg-vmdg505-bbt062-b.cm
Primary Downstream Service Flow
SFID 66126
Max Traffic Rate 402500089
Primary Upstream Service Flow
SFID 66125
Max Traffic Rate 38500089

[Tomo72]

Network Log
Date And Time Error Number Event Description
2017-12-12 05:33:31.00 68010100 DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-12-13 13:03:34.00 68010400 DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:43.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-01-18 21:08:33.00 2417164308 Unit has been restored to factory defaults from a software issued command;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:27.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:27.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:40.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:26.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:26.00 84020300 MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-02-02 22:09:43.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 10:51:01.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 10:51:08.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 10:51:08.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 10:51:09.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 10:51:09.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 10:51:12.00 84020200 Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 10:51:12.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:34.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 11:11:23.00 68010300 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2021-11-29 13:47:13.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[risc19]

---

@Tomo72 wrote:

The only problem is this;

---

Wow. That’s a quality connection right there. 🤦‍♂️

[Tomo72]

My old hub BQM looked fine, the Hub3 is bad and I think it is the firmware